sieve issues
    Schmehl, Paul L 
    pauls at utdallas.edu
       
    Thu Sep 12 16:10:34 EDT 2002
    
    
  
This is just a thought, Brian.  I was having the exact same problem, and
I solved it by symlinking all the individual files in /usr/lib/sasl2.
Originally I symlinked the sasl2 directories like this:
# ln -s /usr/local/lib/sasl2/ /usr/lib/sasl2/
What fixed the sieve problem was:
# ln -s /usr/local/lib/sasl2/* /usr/lib/sasl2/
Paul Schmehl (pauls at utdallas.edu)
Department Coordinator
The University of Texas at Dallas
AVIEN Founding Member
http://www.utdallas.edu/~pauls/
> -----Original Message-----
> From: Brian [mailto:brianb at sboss.net] 
> Sent: Thursday, September 12, 2002 2:13 PM
> To: info-cyrus at lists.andrew.cmu.edu
> Subject: Re: sieve issues
> 
> 
> On Thu, 2002-09-12 at 15:10, Brian wrote:
> 
> > > What sieve client and SASL mechanism caused this message?
> 
> Also, I allow plain logins, so I used the account password.
> 
> # Allow plaintext logins by default (SASL PLAIN)
> allowplaintext: yes
> 
> -- 
> Brian
> 
    
    
More information about the Info-cyrus
mailing list