> Is IMAP auth-ing OK with PLAIN? What's your sasl_minimum_layer? I
> thought
> "1" was low enough, but you may need to try "0".
Thanks man but I saw a thread on that in the archives and already gave it
a shot. No better I'm afraid.
I'm fairly sure that the compile is correct after all my testing
Is IMAP auth-ing OK with PLAIN? What's your sasl_minimum_layer? I thought
"1" was low enough, but you may need to try "0".
On Oct 14 Nick Fisher wrote:
>Dammit I spoke too soon. On closer inspection of the output and some
>jiggering around I find that's not the problem.
>timsieve was finding th
> > > > Did you configure "sieve" as a PAM service?
> > > Uh I'm not sure. How would I tell? How would one do that?
> > > I'm running Gentoo and using it's ports system. It makes life alot
> > easyer
> > > but I'm never sure what options are used at compile time not to
> > > mention that I
> > > Did you configure "sieve" as a PAM service?
> > Uh I'm not sure. How would I tell? How would one do that?
> > I'm running Gentoo and using it's ports system. It makes life alot
> easyer
> > but I'm never sure what options are used at compile time not to
> > mention that I'm running w
On Mon, 14 Oct 2002, Nick Fisher wrote:
> > Did you configure "sieve" as a PAM service?
> Uh I'm not sure. How would I tell? How would one do that?
> I'm running Gentoo and using it's ports system. It makes life alot easyer
> but I'm never sure what options are used at compile time not to
On Mon, 14 Oct 2002, Nick Fisher wrote:
> Hummm.. the plot thickens.
> According to strace sieveshell is happily opening several of the files in
> /usr/lib/sasl2/ as read only. So.
> I'm guessing that sieveshell isn't finding the plugin it wants? I'm trying
> to use pam_mysql with sieve l
> When I had this problem I strace'ed the process to see where it was
> looking
> for the plugins, I think that helped me a lot.
Hummm.. the plot thickens.
According to strace sieveshell is happily opening several of the files in
/usr/lib/sasl2/ as read only. So.
I'm guessing that sievesh
--On Monday, October 14, 2002 14:59 -0400 Nick Fisher <[EMAIL PROTECTED]>
wrote:
> Please excuse me if I'm being silly but what directory and permissions?
> /usr/lib/sasl2/ are o+rx is that what your talking about? Is that
> right? I can't imagine that you need o+w
That is right, is the dir
--On Monday, October 14, 2002 15:08 -0400 Nick Fisher <[EMAIL PROTECTED]>
wrote:
> Yeah... the group is 'root' though.
Shouldn't matter.
When I had this problem I strace'ed the process to see where it was looking
for the plugins, I think that helped me a lot.
Alec
--
Alec H. Peterson -- [EM
Make sure the permissions on that directory and the files in that directory
are set properly.
Alec
--On Monday, October 14, 2002 13:27 -0400 Nick Fisher <[EMAIL PROTECTED]>
wrote:
> Hello people,
> I'm having a problem with sieveshell. When I run 'sieveshell localhost'
> I get:
> connecting
I can't say I know enough about SASL to know why, but I needed the "LOGIN"
mech to make sieve work on my system. HTH
Dave
On Mon, 14 Oct 2002, Nick Fisher wrote:
> Hello people,
> I'm having a problem with sieveshell. When I run 'sieveshell localhost'
> I get:
> connecting to localh
Hello people,
I'm having a problem with sieveshell. When I run 'sieveshell localhost'
I get:
connecting to localhost
unable to connect to server: sasl mech list empty at /usr/bin/sieveshell
line 175.
And when I 'telnet localhost sieve' I get:
Trying 127.0.0.1...
Connected to localhost.
Escape c
12 matches
Mail list logo
