Home › Forums › OS X Server and Client Discussion › Mail › Could not log on to timsieved daemon
- This topic has 6 replies, 3 voices, and was last updated 15 years, 11 months ago by
[email protected].
-
AuthorPosts
-
August 25, 2004 at 7:31 pm #358911
rgnelson
ParticipantI am trying to get Server-side Mail processing for Cyrus running.
I need to be able to use the autorespoder.I’ve seen reference to this error, on this board and others through google search, but I have not run across the fix for it.
“Could not log on to timsieved daemon on your IMAP server localhost.
Please contact your administrator.”I used this article to install: https://www.afp548.com/article.php?story=20040721014726822
When I login to squirrelmail, I see the filters button but when I select it I get the above error.
I have been using squirrelmail successfully for months.
In squirrelmail/conf.pl I have avelsieve listed as an installed plugin.
In squirrelmail/conf.pl the imap port is to 143?Thanks for your help,
RGNelsonSeptember 2, 2004 at 2:07 pm #358970rgnelson
ParticipantI got it to work.
Wrong auth type selected in conf.pl.September 2, 2004 at 4:10 pm #358975Anonymous
GuestCould you be a bit more specific? Are you saying that Squirrelmail’s auth needs type to be something other than “login”. Or that sieve needs to match that login type?
June 27, 2005 at 4:11 am #362121Anonymous
GuestIf you are using debian sarge, don’t forget to install the libsasl2-modules package, without it you can not use plain authentication with timsieved.
December 30, 2005 at 12:52 am #364581maximxygo
ParticipantHeya everybody, I just solved my own issue with "Could not log on to timsieved daemon on your IMAP server…"
What was happening in my case was that only certain users couldn’t use the Filters in Squirrelmail… most could but some, after clicking the Filter link, would get the dreaded error message. After digging around, I found that, in the /usr/sieve folder, the folder "j" (the username was "jritchie") had different permissions than that of the others, who were working.
mail:/usr/sieve root# ls -l
total 0
drwx—— 3 cyrusima wheel 102 Dec 27 15:21 c
drwx—— 4 cyrusima wheel 136 Dec 22 09:49 d
drwx—— 5 cyrusima wheel 170 Dec 23 10:01 e
drw——- 3 cyrusima mail 102 Aug 23 14:36 j
drwx—— 5 cyrusima wheel 170 Dec 23 16:14 k… So, I threw:
mail:/usr/sieve root# chown -R cyrusimap:wheel j
… then:
mail:/usr/sieve root# chmod -R 700 j… to repair the permissions. Resulting in:
mail:/usr/sieve root# ls -l
total 0
drwx—— 3 cyrusima wheel 102 Dec 27 15:21 c
drwx—— 4 cyrusima wheel 136 Dec 22 09:49 d
drwx—— 5 cyrusima wheel 170 Dec 23 10:01 e
drwx—— 3 cyrusima wheel 102 Aug 23 14:36 j
drwx—— 5 cyrusima wheel 170 Dec 23 16:14 kWorked like a charm. 🙂
mark daniel
detroitmac
http://www.detroitmac.comAugust 10, 2006 at 9:06 pm #366791Anonymous
Guest[QUOTE][u]Quote by: RGNelson[/u]
I got it to work.
Wrong auth type selected in conf.pl.[/QUOTE]
I don’t understand. I’m looking in conf.pl (several years later, mind you 😕 ) and don’t see an option for an auth type. If this is what truly fixes this, I’m interested in knowing how to change it.
May 6, 2009 at 11:30 pm #376128[email protected]
Participant/etc/squirrelmail/config/conf.pl
Select Server Settings
Select General… number 6 is your auth type….
-
AuthorPosts
- You must be logged in to reply to this topic.
Comments are closed