kolabmailboxfilter.php vcard problems
Simon Barrett
simon.barrett at jinny.ie
Tue Jul 17 18:04:37 CEST 2007
Hi All,
I hope you can help. I've recently taken over the administration of a kolab
installation. I believe the original idea was to make full use of the
groupware functions, but few have been implemented.
I'm having a problem with mails containing vcard information, in that they are
not being delivered to the users. The postfix log shows the following errors
(I've changed company specific names):
...
Jul 16 17:02:13 mserver <warning> postfix/pipe[31088]: warning:
pipe_command_wait_or_kill: child wait time limit exceeded
Jul 16 17:02:13 mserver <info> postfix/pipe[31088]: E312C33E66:
to=<test.user at example.com>, relay=kolabmailboxfilter, delay=1001,
status=bounced
(Command time limit exceeded: "/kolab/bin/php".
Command output:
PHP Warning: file_get_contents(/kolab/etc/kolab/res_priv.pem):
failed to open stream: Permission denied
in /kolab/var/kolab/php/kolabfilter/resmgr.php on line 185
PHP Warning: openssl_private_decrypt(): key parameter is not a valid private
key in /kolab/var/kolab/php/kolabfilter/resmgr.php on line 192
PHP Warning: openssl_free_key() expects parameter 1 to be resource,
integer given in /kolab/var/kolab/php/kolabfilter/resmgr.php on line 199
PHP Warning: array_key_exists(): The second argument should be either an
array or an object in /kolab/var/kolab/php/kolabfilter/resmgr.php on line 212
PHP Warning: feof(): supplied argument is not a valid stream resource
in /kolab/var/kolab/php/kolabfilter/resmgr.php on line 281
PHP Warning: fread(): supplied argument is not a valid stream resource
in /kolab/var/^@
Jul 16 17:02:13 mserver <info> postfix/clean
up[32270]: 7D98333E94:
message-id=<20070716160213.7D98333E94 at mserver.example.com>
Jul 16 17:02:13 mserver <info> postfix/qmgr[7776]: 7D98333E94: from=<>,
size=15039, nrcpt=1 (queue active)
...
I've checked resmgr.log and it shows the following:
July 16 16:45:32 kolabfilter.php[31130]: Debug: Kolabfilter starting up,
sender=sender at example2.com, recipients=test.user at example.com,
client_address=xxx.xxx.xxx.xxx
July 16 16:45:33 kolabfilter.php[31130]: Debug: Kolabfilter successfully
completed
July 16 16:45:33 kolabmailboxfilter.php[31131]: Debug: Kolabmailboxfilter
starting up, sender=sender at example2.com, recipients=test.user at example.com,
client_address=127.0.0.1
July 16 16:45:33 kolabmailboxfilter.php[31131]: Debug: Found iCal data in
message
July 16 16:45:33 kolabmailboxfilter.php[31131]: Debug: Calling resmgr_filter(
sender at example2.com,
test.user at example.com, /kolab/var/resmgr/filter/IN.Aqndjn )
July 16 16:45:33 kolabmailboxfilter.php[31131]:
getLDAPData(sender at example2.com,test.user at example.com)
July 16 16:45:33 kolabmailboxfilter.php[31131]: Error reading private key:
error:0906D06C:PEM routines:PEM_read_bio:no start line
July 16 16:45:33 kolabmailboxfilter.php[31131]: Error decrypting password:
error:0906D06C:PEM routines:PEM_read_bio:no start line
July 16 16:45:33 kolabmailboxfilter.php[31131]: Debug: Action for
sender at example2.com is Array
I've checked /kolab/var/resmgr/filter/ and it seems to be the final resting
place of any vcard message. I'm still finding my feet with this, and at this
stage I'm stuck. I've looked for anything relating to this in the archives,
but I've had no luck. At a guess, I'd say that there's an ldap dependency
for vcard functionality that may have been a requirement during the original
installation but is no longer accessible due to a misconfiguration.
Judging by the number of files in /kolab/var/resmgr/filter/ these users have
been unable to get emails with vcard info for some months. As an interim fix,
I wouldn't mind switching off the ldap - vcard functionality and have the
messages deliver like ordinary messages. This should give me time to
look into the problem more thoroughly.
Does anyone have any ideas? Kolab v2.0.4 on Debian.
Thanks & regards,
Simon
More information about the users
mailing list