Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

102.7.0: Sogo calendar and tasks do not sychronize new items from outside

  • 2 antwoorde
  • 0 hierdie probleem
  • 1 view
  • Laaste antwoord deur gerhard20

more options

I face the strange behavior that items added with TB to calendar or tasks which will be synchronized, but those which are made on my tablet or mobile won´t be brought into TB although I can see them in SoGo web interface.

I am using the native CalDAV and CardDAV solution in TB.

Can somebody help?

I face the strange behavior that items added with TB to calendar or tasks which will be synchronized, but those which are made on my tablet or mobile won´t be brought into TB although I can see them in SoGo web interface. I am using the native CalDAV and CardDAV solution in TB. Can somebody help?

Gekose oplossing

The problem was AVAST which denied incoming db entries..... solved. sorry.

Lees dié antwoord in konteks 👍 0

All Replies (2)

more options

this is one example of an event which is not synchronized:

BEGIN:VCALENDAR PRODID:DAVx5/4.3-gplay ical4j/3.2.7 (com.samsung.android.calendar) VERSION:2.0 BEGIN:VTIMEZONE TZID:Europe/Berlin LAST-MODIFIED:20221105T024526Z BEGIN:DAYLIGHT TZNAME:CEST TZOFFSETFROM:+0100 TZOFFSETTO:+0200 DTSTART:19810329T020000 RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU END:DAYLIGHT BEGIN:STANDARD TZNAME:CET TZOFFSETFROM:+0200 TZOFFSETTO:+0100 DTSTART:19961027T030000 RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU END:STANDARD END:VTIMEZONE BEGIN:VEVENT DTSTAMP:20230221T101532Z UID:CF947EB00E2E4CA385EE9158478B301B0 SEQUENCE:1 SUMMARY:Testevent DTSTART;TZID=Europe/Berlin:20230224T111500 DTEND;TZID=Europe/Berlin:20230224T121500 CLASS:PUBLIC BEGIN:VALARM TRIGGER:-PT1M ACTION:DISPLAY DESCRIPTION:Testevent END:VALARM END:VEVENT END:VCALENDAR

more options

Gekose oplossing

The problem was AVAST which denied incoming db entries..... solved. sorry.