Calendar events hosted on MailEnable Pro 3.6 do not show up because of missing ALLDAYEVENT tag

RESOLVED INCOMPLETE

Status

Calendar
Provider: CalDAV
RESOLVED INCOMPLETE
9 years ago
8 years ago

People

(Reporter: Will Godfrey, Unassigned)

Tracking

Lightning 0.9
x86
Mac OS X

Details

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729)
Build Identifier: Lighting 0.9 build 2008091721

I am running Mac OS X 10.5.6, Thunderbird 2.0.0.21 build 20090302, and Lighting 0.9 build 2008091721 on my desktop client.  I am attempting to sync with my calendar hosting on my MailEnable Professional 3.6 server running on Windows 2003 Server.

Using these instructions: http://www.mailenable.com/documentation/webmail/webframe.html?Integrated_Mailbox_Calendar.html, I have gotten Lightning to synchronize my calendars hosted on my MailEnable server, except that MailEnable's webmail calendar will not display events created in Lighting.  The .CAL files are posted to the server, but MailEnable will not display them because, when an event is NOT an all day event, Lighting omits the <ALLDAYEVENT>0</ALLDAYEVENT> tag, rather that explicitly setting it to zero.  MailEnable's calendar apparently requires this.  As soon as I add this tag to the XML for the event stored in Postoffices\mydomain\MAILROOT\myuser\Calendar\_index.xml, the event will appear in the MailEnable web calendar view.

If I create an all day event in Lighting and sync it, the event WILL appear in MailEnable web calendar, because the <ALLDAYEVENT> tag is present.

So, it seems that MailEnable requires that the tag <ALLDAYEVENT> be explicitly set to 0, rather than simply omitted, when the event is not an all-day event.

If you'd like Lighting to be compatible with this popular mail/calendar server, you might want to add this to the software.

Reproducible: Always

Steps to Reproduce:
1. Set up Lighting to sync with MailEnable calendar with the instructions posted here: http://www.mailenable.com/documentation/webmail/webframe.html?Integrated_Mailbox_Calendar.html

2. Create a new calendar, hosted on the network, with the address http://server:8080/calendar/.

3. Place two events on this calendar.  One as an all-day event, and one not.

4. Log into MailEnable web mail and click "Calendar"  Only the all-day event will appear.  However, if you look at the actual text file of the calendar event on the MailEnable web server at {MAILENABLE ROOT}\Postoffices\mydomain\MAILROOT\myuser\Calendar, both events will be there.

5. Edit the _index.xml file.  Find the XML for the missing event, and add <ALLDAYEVENT>0</ALLDAYEVENT> to the entry.  Save the file

6. Go back to MailEnable Webmail.  The missing event shows up.
Actual Results:  
When entering an event in Lighting that is synced with a MailEnable calendar, only all-day events show up in MailEnable webmail.

Expected Results:  
An event created in Lighting in a calendar that is synced with a MailEnable mail and calendar server, and is NOT an all day event, should show up in the MailEnable web interface when the calendar is viewed.  It does not.

I have not tried to reproduce this problem on Windows.  I will do so and report back.  If you will contact me privately via e-mail, I will provide credentials to a test account on our MailEnable mail/calendar server.  Thanks!

Comment 1

9 years ago
According to the link above CalDAV is used to access the server, updating component to CalDAV provider. 

Without further looking at this issue I'd blame the MailEnable Professional 3.6 server. Based on your description it seems that the server converts from the received iCalendar format to some custom XML format. During conversion it doesn't create the custom ALLDAYEVENT entry for non-all-day events.
Component: Lightning Only → Provider: CalDAV
QA Contact: lightning → caldav-provider
Version: unspecified → Lightning 0.9
Will, have you tried to contact the creator of MailEnable based on Stefan's analysis in comment#1?
No reponse from reporter to comment#2. Feel free to re-open if you have any new information. -> INCOMPLETE
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.