Re: [gentoo-user] emerge of latest qmail seems to have broken mail delivery
I have posted the fix to this to:
http://bugs.gentoo.org/show_bug.cgi?id=34646
The problem WAS as bug in qmail-pop3d.c that was released with
qmail-1.03. Until a fix is released, this can be fixed by
'consumers' as follows:
ebuild /usr/portage/net-mail/qmail/qmail-1.03-r13.ebuild unpack
#make the change to qmail-pop3d.c referenced in the above bug
ebuild /usr/portage/net-mail/qmail/qmail-1.03-r13.ebuild install
On Fri, 2003-11-28 at 17:15, Lincoln A. Baxter wrote:
> I just submitted the following bug:
> http://bugs.gentoo.org/show_bug.cgi?id=34646
>
> Lincoln
>
>
> On Fri, 2003-11-28 at 14:14, Lincoln A. Baxter wrote:
> > On Fri, 2003-11-28 at 09:23, Lincoln A. Baxter wrote:
> > > On Fri, 2003-11-28 at 08:35, Mike Williams wrote:
> > > > -BEGIN PGP SIGNED MESSAGE-
> > > > Hash: SHA1
> > > >
> > > > On Friday 28 November 2003 13:08, Lincoln A. Baxter wrote:
> > > > > It would appear, that upon emerging the latest qmail (1.03-r13) has
> > > > > broken delivery of mail.
> > > > >
> > > > > It seems the messages are being accepted and sent out.
> > > > > Messages for local deliver are also being accepted, but are not
> > > > > available when one connects with a POP client
> > > > >
> > > > > Upon examination of my maildir, all the messages have been
> > > > > written to the maildir/new/ directory. They are not being moved over to
> > > > > the maildir/cur/ directory.
> > > >
> > > > Messages are supposed to be left in the new directory until they are
> > > > read/viewed, then they are moved to cur.
> > >
> > > Yea, that seems right, I noticed files in my wifes cur directory, which
> > > confused me. I think they are left over from when her MUA was
> > > configured to 'leave messages on the server'.
> > > >
> > > > > Does anyone know what changed in this new qmail (besides the fact that
> > > > > the ebuild wants you to generate ssl keys)... I did this, and it seems
> > > > > to have made no difference. The other major thing I emerged this evening
> > > > > was an new version of gcc, but I doubt this would have broken things.
> > > > >
> > > > > Had any one else had the same problem? and/or know of a fix.
> > > >
> > > > Was your pop server updated at the same time?
> > > > Qmail is still doing the right thing.
> > > >
> > >
> > > Sending mail works just fine. I agree that the problem is with the pop
> > > server. I am using qmail-pop3d. Have been for several years. And bin
> > > through several gentoo updates without a problem. This update replaced
> > > all the run scripts in the supervise directory, and created a bunch of
> > > new config files in the control directory, and left qmail-pop3d broken.
> > >
> > > It appears (based on a troll of the logs) that it is looking for
> > > /etc/tcp.pop3.cdb. Now I need to figure out how to build that file.
> > > Also new with this update, were /etc/tcp.{smtp,qmtp,qmqp}{,.cdb}
> > >
> > > It appears that what ever script built these has overlooked the build of
> > > the tcp.pop3 and tcp.pop3.cdb. So I am off to figure this out (by
> > > reading through the ebuild... I suspect the code the built these files,
> > > is probably in the package config function.
> > >
> > > I will post again when I figure this out.
> > >
> > > But there is little doubt that the developer must not use qmail-pop3d,
> > > or this would not have been released way more broken than any previous
> > > update of qmail, since I have been using gentoo. (just about a year
> > > now).
> > >
> > > Thanks...
> > >
> >
> > Oh, we've made it a little farther. the tcprules program is used to
> > build the /etc/tcp.pop3.cdb file as follows:
> >
> > tcprules /etc/tcp.pop3.cdb /etc/tcp.pop3.tmp >
> > Once one creates this file, connections to the pop3 server are accepted.
> > But we hang on the connection to the pop3 server.
> >
> > In the new configuration files the POP3 server is configured to call
> > /bin/checkpassword. I am pretty sure was was before too. I have tested
> > by telneting to port 110, and authenticating with
> >
> > user NAME
> > pass PASSWORD
> >
> > and
> > list
> > quit
> >
> > which returns a list of mails and sizes, and quits just fine. So now I
> > think pop3d IS working correctly. And it is evolution that is
> > misbehaving.
> >
> > So I reconfigure EVO a 100 times, starting from scratch, and it just
> > HANGS talking to the qmail-pop3d. I configure EVO to talk to my ISP,
> > and it works first time. Its not the EVO config, its gotta be the new
> > qmail-pop3d server.
> >
> > Lincoln
> >
> >
> >
> > --
> > [EMAIL PROTECTED] mailing list
> >
>
>
> --
> [EMAIL PROTECTED] mailing list
--
Lincoln A. Baxter <[EMAIL PROTECTED]>
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-user] emerge of latest qmail seems to have broken mail delivery
I just submitted the following bug:
http://bugs.gentoo.org/show_bug.cgi?id=34646
Lincoln
On Fri, 2003-11-28 at 14:14, Lincoln A. Baxter wrote:
> On Fri, 2003-11-28 at 09:23, Lincoln A. Baxter wrote:
> > On Fri, 2003-11-28 at 08:35, Mike Williams wrote:
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA1
> > >
> > > On Friday 28 November 2003 13:08, Lincoln A. Baxter wrote:
> > > > It would appear, that upon emerging the latest qmail (1.03-r13) has
> > > > broken delivery of mail.
> > > >
> > > > It seems the messages are being accepted and sent out.
> > > > Messages for local deliver are also being accepted, but are not
> > > > available when one connects with a POP client
> > > >
> > > > Upon examination of my maildir, all the messages have been
> > > > written to the maildir/new/ directory. They are not being moved over to
> > > > the maildir/cur/ directory.
> > >
> > > Messages are supposed to be left in the new directory until they are
> > > read/viewed, then they are moved to cur.
> >
> > Yea, that seems right, I noticed files in my wifes cur directory, which
> > confused me. I think they are left over from when her MUA was
> > configured to 'leave messages on the server'.
> > >
> > > > Does anyone know what changed in this new qmail (besides the fact that
> > > > the ebuild wants you to generate ssl keys)... I did this, and it seems
> > > > to have made no difference. The other major thing I emerged this evening
> > > > was an new version of gcc, but I doubt this would have broken things.
> > > >
> > > > Had any one else had the same problem? and/or know of a fix.
> > >
> > > Was your pop server updated at the same time?
> > > Qmail is still doing the right thing.
> > >
> >
> > Sending mail works just fine. I agree that the problem is with the pop
> > server. I am using qmail-pop3d. Have been for several years. And bin
> > through several gentoo updates without a problem. This update replaced
> > all the run scripts in the supervise directory, and created a bunch of
> > new config files in the control directory, and left qmail-pop3d broken.
> >
> > It appears (based on a troll of the logs) that it is looking for
> > /etc/tcp.pop3.cdb. Now I need to figure out how to build that file.
> > Also new with this update, were /etc/tcp.{smtp,qmtp,qmqp}{,.cdb}
> >
> > It appears that what ever script built these has overlooked the build of
> > the tcp.pop3 and tcp.pop3.cdb. So I am off to figure this out (by
> > reading through the ebuild... I suspect the code the built these files,
> > is probably in the package config function.
> >
> > I will post again when I figure this out.
> >
> > But there is little doubt that the developer must not use qmail-pop3d,
> > or this would not have been released way more broken than any previous
> > update of qmail, since I have been using gentoo. (just about a year
> > now).
> >
> > Thanks...
> >
>
> Oh, we've made it a little farther. the tcprules program is used to
> build the /etc/tcp.pop3.cdb file as follows:
>
> tcprules /etc/tcp.pop3.cdb /etc/tcp.pop3.tmp
> Once one creates this file, connections to the pop3 server are accepted.
> But we hang on the connection to the pop3 server.
>
> In the new configuration files the POP3 server is configured to call
> /bin/checkpassword. I am pretty sure was was before too. I have tested
> by telneting to port 110, and authenticating with
>
> user NAME
> pass PASSWORD
>
> and
> list
> quit
>
> which returns a list of mails and sizes, and quits just fine. So now I
> think pop3d IS working correctly. And it is evolution that is
> misbehaving.
>
> So I reconfigure EVO a 100 times, starting from scratch, and it just
> HANGS talking to the qmail-pop3d. I configure EVO to talk to my ISP,
> and it works first time. Its not the EVO config, its gotta be the new
> qmail-pop3d server.
>
> Lincoln
>
>
>
> --
> [EMAIL PROTECTED] mailing list
>
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-user] emerge of latest qmail seems to have broken mail delivery
On Fri, 2003-11-28 at 09:23, Lincoln A. Baxter wrote:
> On Fri, 2003-11-28 at 08:35, Mike Williams wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > On Friday 28 November 2003 13:08, Lincoln A. Baxter wrote:
> > > It would appear, that upon emerging the latest qmail (1.03-r13) has
> > > broken delivery of mail.
> > >
> > > It seems the messages are being accepted and sent out.
> > > Messages for local deliver are also being accepted, but are not
> > > available when one connects with a POP client
> > >
> > > Upon examination of my maildir, all the messages have been
> > > written to the maildir/new/ directory. They are not being moved over to
> > > the maildir/cur/ directory.
> >
> > Messages are supposed to be left in the new directory until they are
> > read/viewed, then they are moved to cur.
>
> Yea, that seems right, I noticed files in my wifes cur directory, which
> confused me. I think they are left over from when her MUA was
> configured to 'leave messages on the server'.
> >
> > > Does anyone know what changed in this new qmail (besides the fact that
> > > the ebuild wants you to generate ssl keys)... I did this, and it seems
> > > to have made no difference. The other major thing I emerged this evening
> > > was an new version of gcc, but I doubt this would have broken things.
> > >
> > > Had any one else had the same problem? and/or know of a fix.
> >
> > Was your pop server updated at the same time?
> > Qmail is still doing the right thing.
> >
>
> Sending mail works just fine. I agree that the problem is with the pop
> server. I am using qmail-pop3d. Have been for several years. And bin
> through several gentoo updates without a problem. This update replaced
> all the run scripts in the supervise directory, and created a bunch of
> new config files in the control directory, and left qmail-pop3d broken.
>
> It appears (based on a troll of the logs) that it is looking for
> /etc/tcp.pop3.cdb. Now I need to figure out how to build that file.
> Also new with this update, were /etc/tcp.{smtp,qmtp,qmqp}{,.cdb}
>
> It appears that what ever script built these has overlooked the build of
> the tcp.pop3 and tcp.pop3.cdb. So I am off to figure this out (by
> reading through the ebuild... I suspect the code the built these files,
> is probably in the package config function.
>
> I will post again when I figure this out.
>
> But there is little doubt that the developer must not use qmail-pop3d,
> or this would not have been released way more broken than any previous
> update of qmail, since I have been using gentoo. (just about a year
> now).
>
> Thanks...
>
Oh, we've made it a little farther. the tcprules program is used to
build the /etc/tcp.pop3.cdb file as follows:
tcprules /etc/tcp.pop3.cdb /etc/tcp.pop3.tmp
Re: [gentoo-user] emerge of latest qmail seems to have broken mail delivery
On Fri, 2003-11-28 at 08:35, Mike Williams wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Friday 28 November 2003 13:08, Lincoln A. Baxter wrote:
> > It would appear, that upon emerging the latest qmail (1.03-r13) has
> > broken delivery of mail.
> >
> > It seems the messages are being accepted and sent out.
> > Messages for local deliver are also being accepted, but are not
> > available when one connects with a POP client
> >
> > Upon examination of my maildir, all the messages have been
> > written to the maildir/new/ directory. They are not being moved over to
> > the maildir/cur/ directory.
>
> Messages are supposed to be left in the new directory until they are
> read/viewed, then they are moved to cur.
Yea, that seems right, I noticed files in my wifes cur directory, which
confused me. I think they are left over from when her MUA was
configured to 'leave messages on the server'.
>
> > Does anyone know what changed in this new qmail (besides the fact that
> > the ebuild wants you to generate ssl keys)... I did this, and it seems
> > to have made no difference. The other major thing I emerged this evening
> > was an new version of gcc, but I doubt this would have broken things.
> >
> > Had any one else had the same problem? and/or know of a fix.
>
> Was your pop server updated at the same time?
> Qmail is still doing the right thing.
>
Sending mail works just fine. I agree that the problem is with the pop
server. I am using qmail-pop3d. Have been for several years. And bin
through several gentoo updates without a problem. This update replaced
all the run scripts in the supervise directory, and created a bunch of
new config files in the control directory, and left qmail-pop3d broken.
It appears (based on a troll of the logs) that it is looking for
/etc/tcp.pop3.cdb. Now I need to figure out how to build that file.
Also new with this update, were /etc/tcp.{smtp,qmtp,qmqp}{,.cdb}
It appears that what ever script built these has overlooked the build of
the tcp.pop3 and tcp.pop3.cdb. So I am off to figure this out (by
reading through the ebuild... I suspect the code the built these files,
is probably in the package config function.
I will post again when I figure this out.
But there is little doubt that the developer must not use qmail-pop3d,
or this would not have been released way more broken than any previous
update of qmail, since I have been using gentoo. (just about a year
now).
Thanks...
> - --
> Mike Williams
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.2.3 (GNU/Linux)
>
> iD8DBQE/x081InuLMrk7bIwRAvMaAJ9MZz86WbMvWMjQAlMtoz+XX51bIgCgqQ0+
> i5CICClYjwvECNR6PlP/6lI=
> =EuyH
> -END PGP SIGNATURE-
>
> --
> [EMAIL PROTECTED] mailing list
>
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-user] emerge of latest qmail seems to have broken mail delivery
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 28 November 2003 13:08, Lincoln A. Baxter wrote: > It would appear, that upon emerging the latest qmail (1.03-r13) has > broken delivery of mail. > > It seems the messages are being accepted and sent out. > Messages for local deliver are also being accepted, but are not > available when one connects with a POP client > > Upon examination of my maildir, all the messages have been > written to the maildir/new/ directory. They are not being moved over to > the maildir/cur/ directory. Messages are supposed to be left in the new directory until they are read/viewed, then they are moved to cur. > Does anyone know what changed in this new qmail (besides the fact that > the ebuild wants you to generate ssl keys)... I did this, and it seems > to have made no difference. The other major thing I emerged this evening > was an new version of gcc, but I doubt this would have broken things. > > Had any one else had the same problem? and/or know of a fix. Was your pop server updated at the same time? Qmail is still doing the right thing. - -- Mike Williams -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/x081InuLMrk7bIwRAvMaAJ9MZz86WbMvWMjQAlMtoz+XX51bIgCgqQ0+ i5CICClYjwvECNR6PlP/6lI= =EuyH -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list
[gentoo-user] emerge of latest qmail seems to have broken mail delivery
It would appear, that upon emerging the latest qmail (1.03-r13) has broken delivery of mail. It seems the messages are being accepted and sent out. Messages for local deliver are also being accepted, but are not available when one connects with a POP client Upon examination of my maildir, all the messages have been written to the maildir/new/ directory. They are not being moved over to the maildir/cur/ directory. Does anyone know what changed in this new qmail (besides the fact that the ebuild wants you to generate ssl keys)... I did this, and it seems to have made no difference. The other major thing I emerged this evening was an new version of gcc, but I doubt this would have broken things. Had any one else had the same problem? and/or know of a fix. Lincoln -- [EMAIL PROTECTED] mailing list
