| Anonymous | Login | 2024-04-16 14:52 MDT |
| Main | My View | View Issues | Change Log | Roadmap | Repositories |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
| 0001036 | ClearCenter | app-zarafa - Zarafa | public | 2013-03-18 12:53 | 2013-04-03 15:04 | ||||||||
| Reporter | dloper | ||||||||||||
| Assigned To | bchambers | ||||||||||||
| Priority | low | Severity | feature | Reproducibility | N/A | ||||||||
| Status | assigned | Resolution | open | ||||||||||
| Platform | OS | OS Version | |||||||||||
| Product Version | 6.4.0 | ||||||||||||
| Target Version | Fixed in Version | ||||||||||||
| Summary | 0001036: Zarafa out of office appears to not work | ||||||||||||
| Description | Under a certain condition, the out of office notification fails to produce responses under both community and professional editions. | ||||||||||||
| Steps To Reproduce | This is typical behavior. By design. | ||||||||||||
| Additional Information | Bug is in testing and discovery. New installations do not seem to demonstrate this bug. The trigger for the condition and workaround are TBD. | ||||||||||||
| Tags | No tags attached. | ||||||||||||
| Attached Files | |||||||||||||
 Relationships |
|
 Relationships |
|
Notes |
|
|
(0000751) dloper (administrator) 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 (administrator) 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 (administrator) 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 (administrator) 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). |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2013-03-18 12:53 | dloper | New Issue | |
| 2013-03-18 12:53 | dloper | Status | new => assigned |
| 2013-03-18 12:53 | dloper | Assigned To | => dloper |
| 2013-03-19 09:47 | dloper | Note Added: 0000751 | |
| 2013-03-19 09:47 | dloper | Summary | Zarafa out of office fails to work from webaccess => Zarafa out of office appears to not work |
| 2013-03-19 09:47 | dloper | Steps to Reproduce Updated | View Revisions |
| 2013-03-19 09:48 | dloper | Severity | minor => feature |
| 2013-03-19 09:48 | dloper | Reproducibility | unable to reproduce => N/A |
| 2013-03-19 11:43 | dloper | Assigned To | dloper => bchambers |
| 2013-03-25 14:18 | dloper | Note Added: 0000763 | |
| 2013-03-25 16:05 | user2 | Target Version | 6.4.0 => 6.4.0 Updates |
| 2013-03-28 14:53 | dloper | Note Added: 0000781 | |
| 2013-03-28 15:34 | user2 | Note Added: 0000783 | |
| 2013-03-28 15:34 | user2 | Target Version | 6.4.0 Updates => |
| 2013-03-28 15:51 | user2 | Note Added: 0000784 | |
| 2013-04-03 10:33 | dloper | Note Added: 0000785 | |
| 2013-04-03 15:04 | user2 | Note Added: 0000786 | |
|
Issue History |