Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Administrators

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 12-20-2009, 04:42 PM
Active Member
 
Posts: 30
Unhappy 6.0.4 broken send function

Hi all,

I've upgraded to 6.0.4 but it seems to have broken my ability to send email from any account with a child account attached to it using +zimbraChildAccount. I can compose an email but when I click send the button is deactivated and nothing else happens. The composer remains on the screen and clicking any other items results in an error or no reaction.

If I remove the child account, the main account can send fine.

There is no errors in zimbra.log or any logs in /opt/zimbra/log that I can see. I've removed all the zimlets to see if they were breaking it but it doesn't seem like they are.

Any ideas anyone? I've opened a case with Zimbra support but apparently I need a "production down" emergency for them to bother responding!

Thansks,
Jon
Reply With Quote
  #2 (permalink)  
Old 12-20-2009, 05:37 PM
Zimbra Employee
 
Posts: 187
Default

Quote:
Originally Posted by jmarriott View Post
Hi all,

I've upgraded to 6.0.4 but it seems to have broken my ability to send email from any account with a child account attached to it using +zimbraChildAccount. I can compose an email but when I click send the button is deactivated and nothing else happens. The composer remains on the screen and clicking any other items results in an error or no reaction.

If I remove the child account, the main account can send fine.

There is no errors in zimbra.log or any logs in /opt/zimbra/log that I can see. I've removed all the zimlets to see if they were breaking it but it doesn't seem like they are.

Any ideas anyone? I've opened a case with Zimbra support but apparently I need a "production down" emergency for them to bother responding!

Thansks,
Jon
It appears like a JavaScript error. If you are using Firefox, after the reproducing the issue, Go to Tools > Error Console > Click on "Errors" button.
And paste whatever you see here.
To get more descriptive error, Open Zimbra with ?dev=1 and then follow the above steps.

Its better to open up a bug in bugzilla(Bugzilla Main Page - Zimbra) with all the details as well.
__________________
Bugzilla - Wiki - Downloads - Before posting... Search!
Reply With Quote
  #3 (permalink)  
Old 12-20-2009, 06:49 PM
Moderator
 
Posts: 1,554
Default

family mailboxes have been broken in 6.0

Bug 37217 – family mailboxes - not working in GnR
Reply With Quote
  #4 (permalink)  
Old 12-21-2009, 12:18 AM
Active Member
 
Posts: 30
Default

Hi rrao,

Thanks for replying. I've attached a screenshot with the errors reported in the Firefox console. I'll open up a bug shortly and attach the info from ?dev=1 too.

bdial, looks like a different bug. When we were on 6.0.3 our child accounts were working mostly ok. There were other assorted bugs afflicting their operation but we could still send email!

Thanks,
Jon
Attached Images
File Type: jpg Screenshot-Error Console.jpg (68.4 KB, 82 views)
Reply With Quote
  #5 (permalink)  
Old 12-21-2009, 01:50 AM
Active Member
 
Posts: 30
Default

I just checked the developers console and although there is plenty of output up until I clicked "send", there is no output after I click send.

Jon
Reply With Quote
  #6 (permalink)  
Old 12-21-2009, 07:58 AM
Active Member
 
Posts: 30
Default

For reference:

Bug 43661 – Presence of a child account breaks mail sending
Reply With Quote
  #7 (permalink)  
Old 12-21-2009, 08:01 AM
Zimbra Consultant & Moderator
 
Posts: 20,312
Default

Quote:
Originally Posted by jmarriott View Post
Don't forget to add your vote to it if you think it's important and also open a support case (if you haven't already) and reference that bug report - they give added weight to it's resolution.
__________________
Regards


Bill
Reply With Quote
  #8 (permalink)  
Old 12-21-2009, 08:06 AM
Active Member
 
Posts: 30
Default

Quote:
Originally Posted by phoenix View Post
Don't forget to add your vote to it if you think it's important and also open a support case (if you haven't already) and reference that bug report - they give added weight to it's resolution.
I have done both, thanks.

I'm a little disappointed that a release shipped with such a major show stopper of a bug in it really.

Is it possible to roll back to 6.0.3?

Thanks,
Jon
Reply With Quote
  #9 (permalink)  
Old 12-21-2009, 08:08 AM
Zimbra Consultant & Moderator
 
Posts: 20,312
Default

Quote:
Originally Posted by jmarriott View Post
Is it possible to roll back to 6.0.3?
No, not unless you have a full backup and it would involve installing the previous release and restoring your users.
__________________
Regards


Bill
Reply With Quote
  #10 (permalink)  
Old 12-22-2009, 06:09 AM
Outstanding Member
 
Posts: 708
Default

For working child accounts, you'd have to roll all the way back to 5.0.21, I think.

Workarounds include:

Logging on to different accounts in different browsers. If you use external LDAP auth, use zimbraAuthFallbackToLocal so that you don't actually have to share passwords.

For shared email, as above, but with an IMAP client.

Folder sharing. Issues with Sender/On Behalf Of/meeting acceptance, but various delegation features new in 6.0.4 make that less painful.

Email forwarding/filters with redirect actions.

We have about 20 unhappy child account users but decided that the benefits of getting 3000+ users to 6.x by end of calendar year outweighed the costs.
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.