> Carsten Hoeger wrote:
>
>>What about this issue:
>>
>>http://asg.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrus&searchterm=request%20info%20until%20later&msg=23996
>>
>>Using 2.2.3 and saslauthd I get the same error.
>>
>>Process 19491 attached - interrupt to quit
>>select(1, [0], NU
On Fri, 16 Jan 2004, Ken Murchison wrote:
> Carsten Hoeger wrote:
>
> > On Thu, Jan 15, Rob Siemborski wrote:
> >
> >
> >>I'm quite pleased to announce the long-awaited stable release of Cyrus
> >>IMAPd 2.2.3. This release contains substantial new features over the 2.1
> >>series including exte
Carsten Hoeger wrote:
On Thu, Jan 15, Rob Siemborski wrote:
I'm quite pleased to announce the long-awaited stable release of Cyrus
IMAPd 2.2.3. This release contains substantial new features over the 2.1
series including extensive support for mailbox annotations, NNTP, much
more stable process ac
Carsten Hoeger wrote:
What about this issue:
http://asg.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrus&searchterm=request%20info%20until%20later&msg=23996
Using 2.2.3 and saslauthd I get the same error.
Process 19491 attached - interrupt to quit
select(1, [0], NULL, NULL, {1480, 44}
[EMAIL PROTECTED] wrote:
Quoting Igor Brezac <[EMAIL PROTECTED]>:
On Wed, 28 Jan 2004 [EMAIL PROTECTED] wrote:
Jan 16 06:59:18 synodon imap[58231]: size read failed
Jan 16 06:59:18 synodon imap[58231]: badlogin: [68.147.210.233]
plaintext
dennis.rendflesh SASL(-1): generic failure: checkpass
It is hard to tell from this. I do not think this is saslauthd problem.
-Igor
On Wed, 28 Jan 2004 [EMAIL PROTECTED] wrote:
> Quoting Igor Brezac <[EMAIL PROTECTED]>:
>
> >
> > On Wed, 28 Jan 2004 [EMAIL PROTECTED] wrote:
> >
> > > > > Jan 16 06:59:18 synodon imap[58231]: size read failed
> > >
Quoting Igor Brezac <[EMAIL PROTECTED]>:
>
> On Wed, 28 Jan 2004 [EMAIL PROTECTED] wrote:
>
> > > > Jan 16 06:59:18 synodon imap[58231]: size read failed
> > > > Jan 16 06:59:18 synodon imap[58231]: badlogin: [68.147.210.233]
> plaintext
> > > > dennis.rendflesh SASL(-1): generic failure: checkp
On Wed, 28 Jan 2004 [EMAIL PROTECTED] wrote:
> > > Jan 16 06:59:18 synodon imap[58231]: size read failed
> > > Jan 16 06:59:18 synodon imap[58231]: badlogin: [68.147.210.233] plaintext
> > > dennis.rendflesh SASL(-1): generic failure: checkpass failed
> > > Jan 16 06:59:24 synodon /kernel: pid 44
> > Jan 16 06:59:18 synodon imap[58231]: size read failed
> > Jan 16 06:59:18 synodon imap[58231]: badlogin: [68.147.210.233] plaintext
> > dennis.rendflesh SASL(-1): generic failure: checkpass failed
> > Jan 16 06:59:24 synodon /kernel: pid 44231 (saslauthd), uid 0: exited on
> > signal 11 (cor
On Fri, Jan 16, Ken Murchison wrote:
> >What about this issue:
> >
> >http://asg.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrus&searchterm=request%20info%20until%20later&msg=23996
> >
> >Using 2.2.3 and saslauthd I get the same error.
[...]
> >using cyrus-sasl-2.1.7
>
> 2.1.7 or 2.1
On Fri, 16 Jan 2004 [EMAIL PROTECTED] wrote:
> >
> > Auch... saslauthd/pam is known to be unreliable, furthermore you cannot
> > use saslauthd/pam combination for fully qualified userids ([EMAIL PROTECTED])
> > because libsasl (2.1.17+) ignores the realm (domain) portion. ;(
> >
>
> But it work
Ted Cabeen wrote:
Rob Siemborski <[EMAIL PROTECTED]> writes:
I'm quite pleased to announce the long-awaited stable release of Cyrus
IMAPd 2.2.3. This release contains substantial new features over the 2.1
series including extensive support for mailbox annotations, NNTP, much
more stable proces
>
> Auch... saslauthd/pam is known to be unreliable, furthermore you cannot
> use saslauthd/pam combination for fully qualified userids ([EMAIL PROTECTED])
> because libsasl (2.1.17+) ignores the realm (domain) portion. ;(
>
But it works just fine with my other 4 servers. I have saslauthd + pa
On Fri, 16 Jan 2004 [EMAIL PROTECTED] wrote:
>
> > The actual code did not change, just the Berkeley detection did. If you
> > remove db 4.1.25 from your system, the sasl configure script should find
> > 4.2.52 (Do not forget to apply a patch from the sleepycat site:
> > http://www.sleepycat.com
> The actual code did not change, just the Berkeley detection did. If you
> remove db 4.1.25 from your system, the sasl configure script should find
> 4.2.52 (Do not forget to apply a patch from the sleepycat site:
> http://www.sleepycat.com/update/4.2.52/patch.4.2.52.html)
>
I'm installing it f
Rob Siemborski <[EMAIL PROTECTED]> writes:
> I'm quite pleased to announce the long-awaited stable release of Cyrus
> IMAPd 2.2.3. This release contains substantial new features over the 2.1
> series including extensive support for mailbox annotations, NNTP, much
> more stable process accounting,
On Fri, 16 Jan 2004 [EMAIL PROTECTED] wrote:
> Quoting Igor Brezac <[EMAIL PROTECTED]>:
>
> >
> > Yes. You need to fetch sasl from CVS or hack the configure script.
> >
>
> OK, that's clear. I'll better wait for new Cyrus SASL release that will support
> BDB 4.2.
The actual code did not change,
Quoting Igor Brezac <[EMAIL PROTECTED]>:
>
> Yes. You need to fetch sasl from CVS or hack the configure script.
>
OK, that's clear. I'll better wait for new Cyrus SASL release that will support
BDB 4.2.
But I have another problem at one of my servers with Cyrus ASL 2.1.17
(I have the same v
On Fri, 16 Jan 2004 [EMAIL PROTECTED] wrote:
>
>
> Hi folks,
>
> If I want to compile Cyrus IMAPD with DBD 4.2 support, and I have Cyrus SASL
> 2.1.17 compiled with DBD 4.1 support, do I need to recompile Cyrus SASL with
> DBD 4.2 support (does it have that support at all)?
Yes. You need to fet
On Fri, Jan 16, 2004 at 01:33:17PM -0700, [EMAIL PROTECTED] wrote:
> If I want to compile Cyrus IMAPD with DBD 4.2 support, and I have Cyrus SASL
> 2.1.17 compiled with DBD 4.1 support, do I need to recompile Cyrus SASL with
> DBD 4.2 support (does it have that support at all)?
That would be wis
Hi folks,
If I want to compile Cyrus IMAPD with DBD 4.2 support, and I have Cyrus SASL
2.1.17 compiled with DBD 4.1 support, do I need to recompile Cyrus SASL with
DBD 4.2 support (does it have that support at all)?
Thank you,
Dmitry
> Carsten Hoeger wrote:
>
>>What about this issue:
>>
>>http://asg.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrus&searchterm=request%20info%20until%20later&msg=23996
>>
>>Using 2.2.3 and saslauthd I get the same error.
>>
>>Process 19491 attached - interrupt to quit
>>select(1, [0], NUL
On Fri, 16 Jan 2004, Ken Murchison wrote:
> Carsten Hoeger wrote:
>
> > On Thu, Jan 15, Rob Siemborski wrote:
> >
> >
> >>I'm quite pleased to announce the long-awaited stable release of Cyrus
> >>IMAPd 2.2.3. This release contains substantial new features over the 2.1
> >>series including exten
Carsten Hoeger wrote:
On Thu, Jan 15, Rob Siemborski wrote:
I'm quite pleased to announce the long-awaited stable release of Cyrus
IMAPd 2.2.3. This release contains substantial new features over the 2.1
series including extensive support for mailbox annotations, NNTP, much
more stable process
Carsten Hoeger wrote:
What about this issue:
http://asg.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrus&searchterm=request%20info%20until%20later&msg=23996
Using 2.2.3 and saslauthd I get the same error.
Process 19491 attached - interrupt to quit
select(1, [0], NULL, NULL, {1480, 440
On Thu, Jan 15, Rob Siemborski wrote:
> I'm quite pleased to announce the long-awaited stable release of Cyrus
> IMAPd 2.2.3. This release contains substantial new features over the 2.1
> series including extensive support for mailbox annotations, NNTP, much
> more stable process accounting, and
On Thu, Jan 15, 2004 at 06:51:36PM -0200, Andreas wrote:
> > But on Gentoo linux distribution db package compiles with --with-uniquename
> > flag.
>
> I don't think this has anything to do with --with-uniquename
Ops, it could indeed, sorry. If this is the cause, then the configure test
should in
Ð ÑÐÐÐÑ ÐÑ Thursday 15 January 2004 23:51 Andreas ÑÐÐ(a):
> On Thu, Jan 15, 2004 at 11:24:35PM +0300, Dmitry P. Schegolev wrote:
> > Hi folks!
> >
> > It's great that cyrus 2.2.3 Released now!
> >
> > > This release also contains support for Berkeley DB 4.2,
> >
> > But on Gentoo linux dist
On Thu, Jan 15, 2004 at 11:24:35PM +0300, Dmitry P. Schegolev wrote:
> Hi folks!
>
> It's great that cyrus 2.2.3 Released now!
>
> > This release also contains support for Berkeley DB 4.2,
>
> But on Gentoo linux distribution db package compiles with --with-uniquename
> flag.
I don't think th
Does config.log show any clues?
-Igor
On Thu, 15 Jan 2004, Dmitry P. Schegolev wrote:
> Hi folks!
>
> It's great that cyrus 2.2.3 Released now!
>
> > This release also contains support for Berkeley DB 4.2,
>
> But on Gentoo linux distribution db package compiles with --with-uniquename
> flag.
Hi folks!
It's great that cyrus 2.2.3 Released now!
> This release also contains support for Berkeley DB 4.2,
But on Gentoo linux distribution db package compiles with --with-uniquename
flag.
And cyrus do not found db:
checking db.h usability... yes
checking db.h presence... yes
checking for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm quite pleased to announce the long-awaited stable release of Cyrus
IMAPd 2.2.3. This release contains substantial new features over the 2.1
series including extensive support for mailbox annotations, NNTP, much
more stable process accounting, and
32 matches
Mail list logo
