- This topic is empty.
-
Posts
-
I have 10.4 server running, but sieve does not work as indicated in the manual. It gives an authentication error using avelsieve and mulberry (an e-mail-client that is capable of using timsieved). Anybody an idea what might be worng? I use IMAP with SSL.
I concur. There has been a problem for a while.
Adding insult to injury, Apple tells you to try sieveshell, which they don’t supply. Thanks, Apple!
And when I picked up sieveshell I noticed this;
zsh 541 [2] % ./sieveshell.pl –user=
localhost
connecting to localhost
Bad protocol from MANAGESIEVE server: EOL2Riiiight.
I checked; created /usr/sieve, chown’ed to cyrusimap:mail (since Apple changed username from cyrus to cyrusimap. I wonder if a large customer had a user named Cyrus and they objected for some reason? 🙂)
Anyway.
I’m still hacking away at it.
I’ll post something here if I get any headway.
From what I gather from the error message the SASL mechanism is not negotiated when it should be. The exact error message is: ‘did not specify mechanism name’. I get this from Mulberry. I am able to login by using telnet to port 2000 though:
Connected to server.jurg.nl.
Escape character is ‘^]’.
“IMPLEMENTATION” “Cyrus timsieved v2.2.12-OS X 10.4.0”
“
“SIEVE” “fileinto reject envelope vacation imapflags notify subaddress relational comparator-i;ascii-numeric regex”
“STARTTLS”
OK
AUTHENTICATE LOGIN
NO “Expected a command. Got something else.”
NO “Did not specify mechanism name”
AUTHENTICATE “LOGIN”
+ VXNlcm5hbWU6
cGV0KXI=
+ UGFzc3dvcmQ6
MWwwdmVvwGVyaWRh
OKNote that the userid and password should be base64 encoded.
MacTroll wrote:
That should be fixable….
IIRC sieve pulls auth mech list from Cyrus.conf buried somewhere in system…
I’m curious if working timsieved binary from 10.3.9 works as it should in 10.4.
I’ve tried adding things to cyrus.conf.
It lives in /etc, it wasn’t buried on my system. Maybe there are multiple copies of it used for some reason? “Yay”.
emory wrote:
MacTroll wrote:
That should be fixable….
IIRC sieve pulls auth mech list from Cyrus.conf buried somewhere in system…
I’m curious if working timsieved binary from 10.3.9 works as it should in 10.4.
I’ve tried adding things to cyrus.conf.
It lives in /etc, it wasn’t buried on my system. Maybe there are multiple copies of it used for some reason? “Yay”.
also – it is actually imapd.conf that governs which auth mechs to try, yes?
I think it must be imapd.conf. Now, I looked at the timsieved package from this site and noticed that authentication works with saslauthd. However, I cannot find saslauthd on 10.4. So 10.4 must use another authentication method. In imapd.conf there is no line with sasl_pwcheck_method. So this is difficult to tell for me (not being an expert on this).
Could this be the issue?
BTW: where did you pick up sieveshell?
In the cyrus imapd source tarball:
cyrus-imapd-2.2.12/perl/sieve/scripts
I was thinking I’d recompile timsieved under Tiger and see if I could make it handle different authentication.
The rub is – the configure script finds Apple’s sasl2 libraries objectionable. I don’t know if I should compile against fink’s or stick to Apple’s.
- You must be logged in to reply to this topic.