Re: cyrus imap playing nicely with pam and Spam assassin

On Mon, 29 Apr 2002, David Wright wrote: > > sasl_pwcheck_method: saslauthd > > You want: > > sasl_pwcheck_method: PAM SASLv2 does not support this option (which is what David is using), saslauthd is the correct option (and running saslauthd -a pam). > Go on from there, and come back when you e

Re: cyrus imap playing nicely with pam and Spam assassin

> I'm trying to make Cyrus IMAP work with Pam for authentication. > sasl_pwcheck_method: saslauthd You want: sasl_pwcheck_method: PAM Go on from there, and come back when you encounter the SASL re-entrancy bug.

RE: Re: SuSE 7.3, IMAP 2.1.3, SASL 2.1.2 -> authentication problem

If you want Plaintext you will need to disable CRAM and DIGEST and SRP/OTP. --On Tuesday, April 30, 2002 12:34 AM -0400 "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Scott, > > Thanks for the help... I believe I will not aware there is such utility > if you don't tell me... =) If you read

RE: Re: SuSE 7.3, IMAP 2.1.3, SASL 2.1.2 -> authentication problem

Scott, Thanks for the help... I believe I will not aware there is such utility if you don't tell me... =) Indeed, I am still encountering the same problem.. and please find what I have done below, 1. run mkimap as root (since error show up if I run as user cyrus) 2. chown -R cyrus:mail /var/

cyrus imap playing nicely with pam and Spam assassin

I'm trying to make Cyrus IMAP work with Pam for authentication. I'm doing this because I'm trying to simplify things for account management for my client. Unfortunately, it's not going well. I have read the fine manual and I've searched the fine Web as well as the archives of this mailing list

Re: Cyrus POP3 sometimes isn't there?

Any help on this? Has anyone had a similar problem? This is something of a show-stopper for us as Cyrus will just occasionally fail. Any help is appreciated, thanks! At 08:08 PM 4/28/2002 -0500, Dustin Puryear wrote: >We seem to be having an odd pop3 issue with Cyrus under FreeBSD. We have >in

Re: "spam" sieve extension

Ken Murchison wrote: >http://www.ietf.org/internet-drafts/draft-segmuller-sieve-relation-01.txt > > Nice! Is this being added to Cyrus? I don't see anything in CVS as yet...

Re: More on SASL/Authentication/Authorization

On Sun, 28 Apr 2002, Kaj J. Niemi wrote: > I'd like to take a look at the code, if it's generally available. Thanks :) > You can find the patch and brief documentation at http://www.ypass.net/cyrus/. -Igor

Re: Bad Shutdown has killed cyrus

I'll second this. I had the same thing happen to me after I had Cyrus 2.1.2 running for about a month. The problem is that if one of the .db files (i.e. mailboxes.db) gets corrupted and you haven't set up a "hot backup" of your db files, the recovery process has to go through EVERY db transaction

Re: snmp questions

Okay, I got snmpd running with agentx support on port 705. However, shouldn't I be able to do a snmpwalk localhost public .1.3.6.1.4.1.3.6.1.2.1 and see the cyrus stats? I get nothing returned. I've got to be missing something simple here. I see snmpd listening on port 705, but nothing (l

Inbox and things

Hi friends! imtest -m login -a andreas localhost C: C01 CAPABILITY S: * OK delta Cyrus IMAP4 v2.1.3 server ready I´m testing Cyrus with squirrelmail (very nice) at the moment and have a question about the INBOX: Ordner Letztes Update: Mon, 17:21 (Ordnerliste aktualisieren) - INBOX (1/15)

Re: SQUAT failed to open index file

"Sweethome.co.il Webmaster" wrote: > > Hi, > > I'm getting this error in the imapd.log when trying to access a mailbox > from IMP 3.1 > > Apr 28 11:05:13 mail01 imapd[10841]: SQUAT failed to open index file > Apr 28 11:05:13 mail01 imapd[10841]: SQUAT failed > > any ideas about a solution?

Re: "spam" sieve extension

Jeremy Howard wrote: > > Marc G. Fournier wrote: > > >Oh, very very cool ... I've been doign it in postfix's content_filter, but > >then its doing *everyone*'s email ... this is soo much better ... > > > >Any chance we'll see this in CVS sometime soon? Maybe in time for 2.1.4?? > > > > >

Re: SQUAT failed to open index file

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 "Sweethome.co.il Webmaster" <[EMAIL PROTECTED]> writes: > Apr 28 11:05:13 mail01 imapd[10841]: SQUAT failed to open index file > Apr 28 11:05:13 mail01 imapd[10841]: SQUAT failed > > any ideas about a solution? Ignore or run squatter via cyrus.conf

Re: SuSE 7.3, IMAP 2.1.3, SASL 2.1.2 -> authentication problem

Some more information to share with you all.. I figure out the error that was previously shown (cannot find db..) is becoz the directories inside /var/imap doesn't exist. I created the following directories and grant the right cyrus:mail to all of them and the error has gone away. /var/imap /

RE: Re: SuSE 7.3, IMAP 2.1.3, SASL 2.1.2 -> authentication problem

Scott, Thanks for the reply. I have tried again to compile SASL and IMAP again, since I suspect it is something related to the use of Berkeley DB4.0 Below please find the log I encountered in /var/log/messages when I try to run "cyradm -u cyrus localhost". Some questions to follow.. 1. Shou

Re: "Segmentation fault" problem

On Mon, 29 Apr 2002, LiuJinhui wrote: > Every I quit the cyradm, I got error message: > Segmentation fault > > mailb:/var/spool/imap# cyradm -u root 202.118.66.103 9100 > Please enter your password: > IMAP Password: > 202.118.66.103> exit > Segmentation fault > ~~

"Segmentation fault" problem

Every I quit the cyradm, I got error message: Segmentation fault mailb:/var/spool/imap# cyradm -u root 202.118.66.103 9100 Please enter your password: IMAP Password: 202.118.66.103> exit Segmentation fault Who can tell me where is the problem? Than

Re: Authentication error with sieveshell

Nicolas Bonnefon schrieb: > > I use Cyrus 2.0.16 with Digest-MD5 SASL authentication on my Linux server > and it works well. But when I try to use sieveshell : > > $ sieveshell -u nicko -a nicko outerspace > connecting to outerspace > Please enter your password: x > unable to connect to se