6.0.4 broken send function

[jmarriott]

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

[rrao]

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.

[bdial]

family mailboxes have been broken in 6.0

Bug 37217 – family mailboxes - not working in GnR

[jmarriott]

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

[jmarriott]

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

[jmarriott]

For reference:

Bug 43661 – Presence of a child account breaks mail sending

[phoenix]

For reference:

Bug 43661 – Presence of a child account breaks mail sending

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.

[jmarriott]

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

[phoenix]

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.

[Rich Graves]

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.