Summary: | akonadi_davgroupware_resource: Error when uploading item: 100 | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Thomas Roemer <tidirium> |
Component: | DAV Resource | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | greg |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Thomas Roemer
2014-09-26 13:47:50 UTC
OK, so if I understand correctly the problem: - you configure the resource to access Zimbra at host mail1.site - the resource fetches the calendars and the events successfully - when you want to write a new event the resource tries to connect to smtp.1und1.de Is that it? Could you post the content of the file ~/.kde4/share/config/akonadi_davgroupware_resource_XXrc, where XX is the resource ID? Feel free to replace the hostname you configured with 'mail1.site'. Also, can you have a look in akonadiconsole (in the 'Browser' tab) the properties of the calendars, especially their remote identifier? Thanks, Grégory The problem doesn't exist in this environment: Repository: openSUSE-12.3-Update Name: kdebase4-session Version: 4.10.5-1.100.1 I will check later on a openSUSE 13.1 platform the actual update. Thanks for your great support in our email communication. But I have not enough time to follow your advise to sniff the communication between imap and akonadi. I have to anonymize the data, as you recommended before. Feel free to close the report... thx a lot At KDE 4.14.3 there is still the same behavior. The plugin resolv the login name and search at my provider try to login with an other hostname as I defined in the settings for the zimbra-server on my intranet. The plugin try to write my new appointment at smtp.1und1.de because my login name at the zimbra server is hosted there. Why is the plugin trying to resolv/expand the loginname to use another login-server as I defined it before?! The problem has been solved. The client ask Zimbra for this "flag": "Hostname of public service" The Zimbra Server deliver the domain that I have configure: The smtp of my provider. Zimbra/configuration/@domain settings: Hostname des öffentlichen Diensts: none Hostname of public service: none This setting should work for internal using (intranet). |