ClearFoundation Tracker - ClearCenter
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001036ClearCenterapp-zarafa - Zarafapublic2013-03-18 12:532013-04-03 15:04
Reporterdloper 
Assigned Tobchambers 
PrioritylowSeverityfeatureReproducibilityN/A
StatusassignedResolutionopen 
PlatformOSOS Version
Product Version6.4.0 
Target VersionFixed in Version 
Summary0001036: Zarafa out of office appears to not work
DescriptionUnder a certain condition, the out of office notification fails to produce responses under both community and professional editions.
Steps To ReproduceThis is typical behavior. By design.
Additional InformationBug is in testing and discovery. New installations do not seem to demonstrate this bug. The trigger for the condition and workaround are TBD.
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2013-03-18 12:53dloperNew Issue
2013-03-18 12:53dloperStatusnew => assigned
2013-03-18 12:53dloperAssigned To => dloper
2013-03-19 09:47dloperNote Added: 0000751
2013-03-19 09:47dloperSummaryZarafa out of office fails to work from webaccess => Zarafa out of office appears to not work
2013-03-19 09:47dloperSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=51#r51
2013-03-19 09:48dloperSeverityminor => feature
2013-03-19 09:48dloperReproducibilityunable to reproduce => N/A
2013-03-19 11:43dloperAssigned Todloper => bchambers
2013-03-25 14:18dloperNote Added: 0000763
2013-03-25 16:05user2Target Version6.4.0 => 6.4.0 Updates
2013-03-28 14:53dloperNote Added: 0000781
2013-03-28 15:34user2Note Added: 0000783
2013-03-28 15:34user2Target Version6.4.0 Updates =>
2013-03-28 15:51user2Note Added: 0000784
2013-04-03 10:33dloperNote Added: 0000785
2013-04-03 15:04user2Note Added: 0000786

Notes
(0000751)
dloper   
2013-03-19 09:47   
This is not a bug but rather the typical behavior. Responses to email messages are governed by the /etc/zarafa/autorespond and the service zarafa-dagent.

Please refer to this guide:

http://www.clearcenter.com/support/documentation/clearos_guides/manipulating_autoresponder_behavior [^]

The manipulation of these values should be created as a feature.
(0000763)
dloper   
2013-03-25 14:18   
I've requested an open ticket with Zarafa on this issue as a followup since alias domains appear still NOT to work for Out of Office in spite of the previous notes which work well for the main or default domain.
(0000781)
dloper   
2013-03-28 14:53   
Zarafa says that this should work...but it doesn't in ClearOS.

Steps to reproduce.

-Configure Zarafa.
-Set up an alias domain in SMTP Server and ensure email to the user works for main domain and alias
-Make a user and log into their web access
-Create and enable out of office message in settings.
-Email alias address (not out of office message)
-Email default address (out of office message)

You may need to tweek the time between messages value according to this:

http://www.clearcenter.com/support/documentation/clearos_guides/manipulating_autoresponder_behavior [^]

Set:
TIMELIMIT=$[5]
(0000783)
user2   
2013-03-28 15:34   
Here are the relevant mail headers for a message sent to alias "testguy" for username "test".

Received: from localhost (localhost [127.0.0.1])
    by mail.example.com (Postfix) with ESMTP id A24F29DD3
    for <test@example.com>; Thu, 28 Mar 2013 17:16:51 -0400 (EDT)
Subject: test out of office
To: testguy@example.com

That looks okay. Will keep digging.
(0000784)
user2   
2013-03-28 15:51   
It looks like Zarafa might need the full e-mail alias in the clearMailAliases LDAP attribute?

http://doc.zarafa.com/6.40/Administrator_Manual/en-US/html/_appendix_b_ldap_attribute_description.html [^]

Cyrus and Google Apps only accept base names (no domain part) for aliases. If Zarafa needs the full e-mail address:

1) A custom mail extension is required
2) Destination domain support becomes messy / complex
(0000785)
dloper   
2013-04-03 10:33   
Adding the full email address to clearMailAliases fixes the issue.

Wouldn't having zarafa tuned for zarafaAliases then be the better solution and have this attribute dynamically tuned to be a composite of clearMailAliases + domain names?
(0000786)
user2   
2013-04-03 15:04   
The "Mail Extension" app used by Google Apps, Cyrus and the current Zarafa would have to be replaced by a "Zarafa Mail Extension". It would be a lot of cut-and-paste code, but not too bad.

I'm assuming the Zarafa code does a direct lookup on the the alias LDAP attribute, so we can't do anything fancy without upstream changes. If an SMTP "destination domain" is added or deleted, all Zarafa user objects would need alias changes (messy).