Help with getting email working: kolab-server-2.2.1-beta-1

[Harkin Banks]

> can you check with cyradm that you actually have an account INBOX for the 
> user
it wants to deliver? (Maybe misstyped the kolab homeserver?)

Yes, there does appear to be an inbox:
user/harkin at example.com (\HasChildren)

# /kolab/bin/cyradm -user manager localhost
Password:
localhost.localdomain> lm
shared.testsharedfolder at example.com (\HasNoChildren)
user/adminstrator/Calendar at example.com (\HasNoChildren)
user/adminstrator/Contacts at example.com (\HasNoChildren)
user/adminstrator/Notes at example.com (\HasNoChildren)
user/adminstrator/Tasks at example.com (\HasNoChildren)
user/adminstrator at example.com (\HasChildren)
user/harkin/Calendar at example.com (\HasNoChildren)
user/harkin/Contacts at example.com (\HasNoChildren)
user/harkin/Notes at example.com (\HasNoChildren)
user/harkin/Sent at example.com (\HasNoChildren)
user/harkin/Tasks at example.com (\HasNoChildren)
user/harkin at example.com (\HasChildren)
user/user1/Calendar at example.com (\HasNoChildren)
user/user1/Contacts at example.com (\HasNoChildren)
user/user1/Notes at example.com (\HasNoChildren)
user/user1/Sent at example.com (\HasNoChildren)
user/user1/Tasks at example.com (\HasNoChildren)
user/user1 at example.com (\HasChildren)


> Maybe misstyped the kolab homeserver?

I'm not sure what you mean by this?


> Also check the logs for kolabmailboxfiler.

Here are the postfix.log entries (not sure if you have another log in 
mind -- please let me know if you do and I will look there) containing 
"kolabmailboxfilter" that I get when attempting to send an email:
[root at smtp kolab]# tail -n100 /kolab/var/postfix/log/postfix.log | grep 
kolabmailboxfilter
Dec 19 16:55:39 smtp.example.com <info> postfix/pipe[17699]: 8A0A45883DA: 
to=<harkin at example.com>, relay=kolabmailboxfilter, delay=0.51, 
delays=0.1/0.08/0/0.34, dsn=5.3.0, status=bounced (Command died with status 
255: "/kolab/bin/php")
Dec 19 16:55:40 smtp.example.com <info> postfix/pipe[17699]: 141605883DE: 
to=<harkin at example.com>, relay=kolabmailboxfilter, delay=1.1, 
delays=0.18/0/0/0.91, dsn=5.3.0, status=bounced (Command died with status 
255: "/kolab/bin/php")
Dec 19 22:18:36 smtp.example.com <info> postfix/pipe[25895]: A1CFB5883DA: 
to=<harkin at example.com>, relay=kolabmailboxfilter, delay=0.67, 
delays=0.27/0.01/0/0.38, dsn=5.3.0, status=bounced (Command died with status 
255: "/kolab/bin/php")
Dec 19 22:18:36 smtp.example.com <info> postfix/pipe[25895]: 50D7E5883DE: 
to=<harkin at example.com>, relay=kolabmailboxfilter, delay=0.67, 
delays=0.18/0/0/0.49, dsn=5.3.0, status=bounced (Command died with status 
255: "/kolab/bin/php")
[root at smtp kolab]#


Another thing is the the LDAP server appears to be running (in a "ps aux"), 
but there is some problem with it such that Horde and Kolab admin are not 
able to communicate with it.  When I restart the Kolab services, it starts 
to work again.


Thank you.


----- Original Message ----- 
From: "Bernhard Reiter" <bernhard at intevation.de>
To: <kolab-users at kolab.org>
Sent: Friday, December 19, 2008 4:21 PM
Subject: Re: Help with getting email working: kolab-server-2.2.1-beta-1

> Dec 19 16:55:39 smtp.example.com <info> postfix/pipe[17699]: 8A0A45883DA:
> to=<harkin at example.com>, relay
> =kolabmailboxfilter, delay=0.51, delays=0.1/0.08/0/0.34, dsn=5.3.0,
> status=bounced (Command died with status 2
> 55: "/kolab/bin/php")

Hmm that looks bad,
can you check with cyradm that you actually have an account INBOX for the 
user
it wants to deliver? (Maybe misstyped the kolab homeserver?)
Also check the logs for kolabmailboxfiler.


> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>