Questions... need Sieve primer

[Florian Gleixner]

Since i had a hard time too to get sieveshell working here my workflow
how i found that out:
Do a telnet to your cyrus server port sieve(2000). It should give you a
hello and the capabilities:

telnet mailserver 2000

"IMPLEMENTATION" "Cyrus timsieved v2.2.13"
"SASL" "GSSAPI LOGIN PLAIN CRAM-MD5 DIGEST-MD5"
"SIEVE" "fileinto reject envelope vacation imapflags notify subaddress
relational comparator-i;ascii-numeric regex"
"STARTTLS"
OK

The second line gives you the auth mechs. I had a problem once where
there were no mechs listed there. The cause was a wrong entry in
imapd.conf in the field sasl_mech_list (which is not documented!).

Check your /var/log/messages while trying to log in. Saslauthd maybe
gives you some hints what she's trying.

try
sieveshell --authname=someusername mailserver:2000

One unsoved problem on my side: It tries some auth mechs and the first
one always fails, so it may be possible that the password is only
accepted on the 2nd or 3rd prompt because the first ones were unusable
mechs.

Flo

Jason Bailey, Sun Advocate Webmaster schrieb:

>>> configdirectory: /var/lib/imap
>>> partition-default: /var/spool/imap
>>> sievedir: /var/lib/sieve
>>> admins: cyrus
>>> allowanonymouslogin: no
>>> reject8bit: no
>>> quotawarn: 90
>>> timeout: 30
>>> poptimeout: 10
>>> dracinterval: 0
>>> drachost: localhost
>>> #sasl_pwcheck_method: saslauthd
>>> lmtp_overquota_perm_failure: no
>>> lmtp_downcase_rcpt: yes
>>> virtdomains: userid
>>> loginrealms: domain1.com domain2.com domain3.com
>>> autocreatequota: 102400
>>> quotawarnkb: 5120
>>> unixhierarchysep: yes
>>> altnamespace: yes
>>> allowplaintext: yes
>>> sasl_pwcheck_method: auxprop
>>> sasl_mech_list: PLAIN LOGIN CRAM-MD5
>>>
>>> saslauthd is set up to use pam and is running (the default config for
>>> the rpm). I have /etc/pam.d/imap and /etc/pam.d/sieve. But given I am
>>> using /etc/sasldb2, shouldn't it look there before defaulting to
>>> saslauthd in the first place?
>>>
>>> I am running SLES 10 on x86_64 (EM64T)
>>>
>>> Jason Bailey, Web/IT Administrator
>>> Sun Advocate / Emery County Progress
>>> webmaster at sunad.com / webmaster at ecprogress.com
>>> (435) 637-0732 (ext 31)
>>>
>>> ----
>>> Cyrus Home Page: http://cyrusimap.web.cmu.edu/
>>> Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
>>> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
>>
> 
> 
> Okay... sieve is per mailbox. That actually works out to my benefit.
> 
> So how do I get sieveshell to let me login? The authentication aspects
> of Cyrus are my weakest spot... I don't know what I'm doing. All I know
> is that it won't let me login. Documentation is spotty at best. What now?
> 
> The imaptest works, logins directly through cyrus (or cyradm, for that
> matter) work fine. But sieveshell doesn't.
> 
> Ideas?
> ----
> Cyrus Home Page: http://cyrusimap.web.cmu.edu/
> Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
>