Home Forums OS X Server and Client Discussion Mail no auto-reply/vacation messages after sieve install

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #358942
    slipstream
    Participant

    I believe I’ve correctly installed and configured sieve according to Joel’s AFP article but when I create a vacation rule, it doesn’t auto-reply to senders. The Filters and Rules Wizard are functional in Squirrelmail and Avelsieve is creating a “default” script with the correct directory structure under /usr/sieve.

    After reading the latest comments at the end of the article and searching the forums, it appears others are having the same problem but nobody has found a solution. Here’s what I’ve attempted or checked so far:

    1. removed /Library/Receipts/timsieved.pkg and re-installed the timsieved.pkg
    2. verified /usr/sieve has cyrus:mail ownership and 700 permissions
    3. verified /usr/lib/sasl2/pwauxprop.* have root:mail ownership and 705 permissions
    4. verified I’m getting “unable to open LA file: /usr/lib/sasl2/pwauxprop.la” errors in the system.log (a good thing according to the timsieved ReadMe)
    5. run `killall saslauthd; /usr/local/saslauthd -a PAM`as root
    6. commented the callbook tcp entry in /etc/services because it shares the same port as seive (2000–not sure if this is necessary) and kill -HUP’ed xinet

    Is there something I’m overlooking? Is there another way to troubleshoot this?

    BTW, I’m running Mac OS X Server 10.3.5..

    #358943
    Anonymous
    Guest

    I don’t have a fix for you, but maybe you can help me. I’m stuck with this error after I log into SM and click the filters link:
    “Could not log on to timsieved daemon on your IMAP server localhost. Please contact your administrator.”
    I read through your check list in this post and I have checked and/or done all that is listed.
    Did you ever get this error?
    If so, how did you fix it?
    I’m sure I’ve missed something simple.
    Thanks
    RGNelson

    #358969
    rgnelson
    Participant

    I got it to work.
    Wrong auth type selected in conf.pl.

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.

Comments are closed