Re: [Kolab-devel] looking to verify/fix a few issues with kolab 3.3 (ptload/freebusy/ssl/wallace)
Matthias Busch <[email protected]>
| Newsgroups | gmane.comp.kde.devel.kolab |
|---|---|
| Message-ID | <[email protected]> |
I managed to find out some stuff by myself and have more information about wallace... - ssl in the roundcube-plugin folder for calendar and adressbook I did find the config files where I could change http to https. now the webclient is showing the caldav urls as https - wallace it apprears that wallace is working when the mail is addressed to the primary email. It does confirm appointments and let mail through when sending an email to secondary addresses, it will get bounced as 550 Nov 14 10:13:16 kolab postfix/lmtp[14345]: 501ED20101: to=<[email protected]>, relay=kolab.domain.tld[/var/lib/imap/socket/lmtp], delay=0.01, delays=0.01/0/0/0.01, dsn=4.1.1, status=SOFTBOUNCE (host kolab.domain.tld[/var/lib/imap/socket/lmtp] said: 550-Mailbox unknown. Either there is no mailbox associated with this 550-name or you do not have authorization to see it. 550 5.1.1 User unknown (in reply to RCPT TO command)) I suspect it has something to do with the ptload errors cropping up... Nov 14 10:12:16 kolab ptloader[4154]: No entries found Nov 14 10:12:16 kolab lmtpunix[3847]: ptload(): bad response from ptloader server: identifier not found Nov 14 10:12:16 kolab lmtpunix[3847]: ptload failed for [email protected] is there nothing I could do to either fix that ptload stuff or at least help gather more information so it can be fixed?