I ran into the same problem. What solved it for me was running this
command.
libtool --finish /usr/lib/sasl
If you are making it from source I would do a make clean, make, then make
install after running it. The first time I installed from source, the make
install told me I needed to do it and
Sendmail 8.12 allows defining of the mailbox database (i.e. so the mailer
flag 'w' will would work with Cyrus).
Is anyone working on creating the functions for sendmail's libsm/mbdb.c to
do this with Cyrus? Sendmail only comes with a functions for /etc/passwd and
LDAP right now.
-
Josh
with cyrtus installed and imap and imaps enabled on pine using the /ssl
oprion it first always tries to use cram-md5 overriding imaps.
There is a way to force pine to use ssl with imaps rather using the
cram-md5 secrets ?
That is if an user is not in the sasldb database it cannot authenticate it
is it possible to compile cyrus without sasl library support ??
my main problem is that both pine and eudora looks for sasldb password
file and cram-md5 authentication before using imaps. If sasl is avaliable
they won't use imaps PLAIN+TLS authentication.
And eudora behave so strange. Before be
Not possible unless you want to mess with customizing the source code.
But you might try building SASL without CRAM-MD5 support (i.e., plain
passwords only). It's not SASL that Pine and Eudora look for, it's the
set of auth machanisms cyrus advertises. If SASL is built without
CRAM, cyrus ca
nice. But ok I Want to force the use of imaps of course I Do not want to
use plain passwords. Anyway how I can disable in the sasl library the
support for CRAM-MD5 ??
is there an option when u build ???
thanks
Rick
On Fri, 30 Mar 2001, Rob Tanner wrote:
> Not possible unless you want to mess
Sure there is, try: "--disable-cram".
--On Friday, March 30, 2001 12:01:00 PM +0200 rj45
<[EMAIL PROTECTED]> wrote:
>
> nice. But ok I Want to force the use of imaps of course I Do not want
> to use plain passwords. Anyway how I can disable in the sasl library
> the support for CRAM-MD5 ??
> i
rj45 wrote:
>
> is it possible to compile cyrus without sasl library support ??
>
> my main problem is that both pine and eudora looks for sasldb password
> file and cram-md5 authentication before using imaps. If sasl is avaliable
> they won't use imaps PLAIN+TLS authentication.
You can use a p
I'm running 1.6.24 on a machine with RedHat 6.2. I routinely see the
problem of messages being deferred because they timeout on their way
into users' mailboxes. deliver is running via lmtp to allow vacation to
work. Is this a known problem? Is there a cure?
ian
[igb@new-elo-relay igb]$ /usr/
When creating a mailbox in cyradm (v2.0.12), it seems that
no ACL's are created at all:
localhost> cm user.test
localhost> lam user.test
localhost>
When running the same commands in v1.6.24, it would at
least create ACL's for the user test:
localhost> cm user.test
localhost> lam user.test
test lr
On Thu, Mar 29, 2001 at 11:01:11PM +0200, Olaf Zaplinski wrote:
> Hi all,
>
> I have 2 Linux machines, they are almost identical:
>
> Kernel 2.2.18
> cyrus-imapd-2.0.12
> cyrus-sasl-1.5.24
> Berkeley DB 3.1.17
> openssl-0.9.6
> sendmail 8.11.3
>
> One is a SuSE 7.1 distro, the Berkeley DB and
What's the best way to move from an mail from an existing (non-IMAP/Berkeley)
mailbox to a Cyrus mailserver if I have to keep all the status information
(Read/Replied etc) intact ?
richard.
---
Richard Offer
richard offer wrote:
>
> What's the best way to move from an mail from an existing (non-IMAP/Berkeley)
> mailbox to a Cyrus mailserver if I have to keep all the status information
> (Read/Replied etc) intact ?
You can try 'mbxcvt' which is part of the imap-utils package located
here:
ftp://ft
The iggest problem I had with mbxcvt was that it kept dying when it found
"non-ascii characters", right around message number 8000 in a 8500 message
mailbox...
Scott
On Fri, 30 Mar 2001, richard offer wrote:
>
> * $ from [EMAIL PROTECTED] at "30-Mar: 3:25pm" | sed "1,$s/^/* /"
> *
> *
> * I ser
* $ from [EMAIL PROTECTED] at "30-Mar: 3:25pm" | sed "1,$s/^/* /"
*
*
* I seriously suggest you give a second thought to using mbxcvt. It's not
* very robust, and it's not that scalable.
*
* Try this:
*
* http://www.oreilly.com/catalog/mimap/chapter/ch09.html
*
I had tried the batch-method fro
I seriously suggest you give a second thought to using mbxcvt. It's not
very robust, and it's not that scalable.
Try this:
http://www.oreilly.com/catalog/mimap/chapter/ch09.html
On Fri, 30 Mar 2001, Ken Murchison wrote:
>
>
> richard offer wrote:
> >
> > What's the best way to move from an ma
While testing Imap, imtest -m login -p imap localhost
I get failure :prot layer failure
In the archives, it looks like it is a common occuranceI could not
find a response on how to deal with that...any
suggestions...Thanks...Sophie
17 matches
Mail list logo