Home Forums OS X Server and Client Discussion Mail Timsieved daemon IMAP logon problem

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #368680
    Joel Davies
    Participant

    Hi! I’m trying to install Avelsieve 1.0.1 in conjunction with SquirrelMail 1.4.5 on a newish OS X Server box running 10.4.8. Followed the directions, including adding

    [code]sieve 2000/tcp #Sieve mail filtering[/code]

    to /etc/services/. Also followed the Avelsieve instructions, as well as SquirrelMail’s plugin activation routine. Am now getting a link in SquirrelMail to Filters, but I get the dread “Could not log on to timsieved daemon on your IMAP server localhost. Please contact your administrator.”

    I’ve reviewed what’s been posted here at AFP before on this topic; I’m just wondering if anybody has yet come up with a [b]definitive[/b] fix. The older posts involve so many suggested workarounds, it’s difficult for me to sort out what will work from what might help me really mess things up a lot, as I’m a command-line neophyte. I haven’t done much to the default install of X Server, so I’m disappointed adding Vacation Reply functionality to web mail has turned into such a bear.

    One thing that strikes me is Port 2000 in /etc/services/ seems to already be designated for some other service (“callbook”). Could that be part of the problem?

    #368684
    Joel Davies
    Participant

    Never mind! Found the answer myself here in the forums at:

    [url]https://www.afp548.com/forum/viewtopic.php?showtopic=9707&mode=&show=5&page=2[/url]

    Sorry! I know I searched AFP548 for “avelsieve” and “timsieved” but I didn’t come across this forum post until I googled “port 2000 callbook”

    Anyway, thanks Ian Butler for summing up everything at that above thread. It seems like the missing element for me was creating the /usr/sieve directory with mkdir, chown and chgrp, per Ian’s Step 1. I’d done all the other steps, so now everything seems to work. What was particularly nice was having some help with how to use telnet to test that sieve was actually running.

    I also went ahead and commented out the pre-existing “callbook” entries for port 2000 in etc/services. Don’t know if that helps, but callbook seems obscure enough I’m hoping it doesn’t hurt.

    I still have a newbie’s curiosity about why Apple’s docs say sieve is enabled, when it’s not enabled until you manually create this directory. Anybody care to comment?

    #369343
    Simple1
    Participant

    How did you go about commenting out callbook protocol ” // ” ?? or did you just remove it? I removed it and tried to telnet but everytime I do I get a big error stating I need to rebuild my mail database, I’ll rather not do it at 120GB. Please anyone if you have any solutions respond.

    #369462
    Joel Davies
    Participant

    I would have commented out using the same character sequence used elsewhere in the file; don’t remember precisely what that is now.

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

Comments are closed