[maximxygo]

Heya 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 k

Worked like a charm. 🙂

mark daniel
detroitmac
http://www.detroitmac.com

[maximxygo]

Heya 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 k

Worked like a charm. 🙂

mark daniel
detroitmac
http://www.detroitmac.com

[maximxygo]

josh brings up a good point: be sure that the subnet of the network your vpn’ing from is different than that of the network you’re vpn’ing into.
TCP is TCP… “routing AFP” isn’t an issue, since it’s just another TCP port/service. It sounds like you’ve got some issues with your vpn service. I would also make sure that your server is at 10.4.3, since it resolves some issues with servermgrd and hrdwared processes running away.

[maximxygo]

Well, it does sound like the Xserve was a good way to go, but as someone who’s been in the Mac-based IT consulting industry for years as I have been, I’ve seen a lot of people make the same mistake you’ve made: thinking that Apple made OS X under-the-hood anything like OS 9 and previous OSs. Fact is, they didn’t make a lot of what you see under the hood of OS X, especially on the server side.
What I would recommend is getting to know OS X Server more before regretting your decision; OS X is *extremely* flexible, and can be configured to do most, if not all of (and much much more), of what you’re looking for it to do. It’s just a matter of learning it yourself, or having a consultant who knows OS X Server come in and do it for you.
To answer your questions, though:
VPN – yes, you need to make use of network routing definitions.
Search Domain – this is what gets tacked onto the end of a hostname that does not have a domain specified (i.e. if your client has been given a search domain of "mydomain.office" and that client is configured to fetch mail from or connect to a server called "myosxbox", that client will automatically try to connect to "myosxbox.mydomain.office."
SMB – look at /etc/smb.conf, /etc/smb.conf.template, and http://samba.org.
Server Admin – What are these "extra characters" you shoehorned into your /library/preferences/com.apple.AppleFileServer.plist or afp.conf files? Do you make it a practice of just inserting characters into conf files arbitrarily? 😉

[Author]

Posts