[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: converting from qpopper

From: Jeff Bailey
Subject: Re: converting from qpopper
Date: Sat, 10 Nov 2001 07:18:54 -0800
User-agent: Mutt/1.2.5i

On Sat, Nov 10, 2001 at 10:09:25AM -0500, Alain Magloire wrote:

> > Fencepost is running qpopper and it's corrupting mail.  They will
> > soon be running our pop3d.

> That's great, but you did not find the cause of the problem :)

Known bug in qmail, reproducable very easily.  I run the autobuilder
for the Debian GNU/Hurd port, and it mails me the build logs for
signing.  After a file gets to be about 200k, it truncates it too

The truncation happens even if the message isn't retrieved, because
the bug occurs when qpopper puts the mailbox back into place.

> The advantage to work on a second drop ".user.pop" is to lesser
> the chance of corruptions and to permits new mail to come in
> despite having a pop session active.

Isn't locking supposed to cope with that?

> > > Note: I think qpopper comes with such a tool.
> > 
> > Yup, popauth.  That's what a few other pop3ds call it too, so we
> > should stick to that.
> > 
> > Hmm..  Should that go in the pop3d directory?  Or a subdir off of that
> > pop3d/popauth?  
> Probably on its own, there is nothing POP specific about this tool
> and can probably be use by other program like comstat or imap4d
> to provide DB support.
> NOTE: Sergey sent mail that he was on it, you may want
> to coordinate with him, to avoid duplications.

I'm writing the extract from qpopper right now, we'll mix together
after, I think.

Sergey, should I pipe into popauth, or write directly to the gdbm
file?  I'm worried that we'll just be increasing the number of places
to make changes if we ever want to do it differently.

I don't know enough about database stuff to know if that's a problem,
or even likely.

Abandon the search for truth; settle for a good fantasy.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]