public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Sullivan <michael@espersunited.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] dovecot problem
Date: Fri, 25 Nov 2005 16:36:13 -0600	[thread overview]
Message-ID: <1132958173.11378.2.camel@camille.espersunited.com> (raw)
In-Reply-To: <20051125193306.38f1929a@krikkit.digimed.co.uk>

On Fri, 2005-11-25 at 19:33 +0000, Neil Bothwick wrote:
> On Fri, 25 Nov 2005 11:52:53 -0600, michael@espersunited.com wrote:
> 
> > I'm having a problem with dovecot.  I upgraded dovecot yesterday to
> > 0.99.14-r1, although dovecot --version still claims to be 0.99.14
> 
> Dovecot is version 0.99.14, the r1 refers to the ebuild revision.
> 
> > Nov 25 11:46:09 bullet pop3-login: fd_send(-1) failed: Broken pipe
> > Nov 25 11:46:09 bullet pop3-login: fd_send(-1) failed: Broken pipe
> > Nov 25 11:46:09 bullet pop3-login: fd_send(-1) failed: Broken pipe
> 
> What version of dovecot were you running before. There was a config file
> format change a while ago (on ~x86, I don't know when it affected
> stable). The source of the error looks familiar, did you update the
> config file after emerging the new version?

I guess I was using version 0.99.13 because I emerged that version of
dovecot and everything works fine now.  When I emerged v0.99.14-r1 and
told it to go ahead and replace /etc/dovecot.conf since I hadn't altered
the previous version.  In what way was I supposed to alter the config
file?

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-11-25 22:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-25 17:52 [gentoo-user] dovecot problem michael
2005-11-25 18:29 ` Holly Bostick
2005-11-25 19:33 ` Neil Bothwick
2005-11-25 22:36   ` Michael Sullivan [this message]
2005-11-26  0:03     ` Neil Bothwick

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=1132958173.11378.2.camel@camille.espersunited.com \
    --to=michael@espersunited.com \
    --cc=gentoo-user@lists.gentoo.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