Sending error

BritTim · 1 May 2015, 12:22 PM

I have a client who, for about the last 24 hours, is experiencing an error every time he sends an email.

In reality, the message is sent successfully. However, the message "Sending" does not disappear from the screen (until he visits a new page) and an error message

Quote:

Sorry, the action could not be completed because a server error has occurred. This error has been logged and will be investigated. ErrorId=47104e04f98131cf-1430449779

is shown in an overlay window at the bottom of the screen until dismissed.

The client in question is a user of the CardDAV support.

I suspect the issue may be related to the new backend support using JMAP.

Is anyone else seeing anything similar?

EDIT: I have created a support ticket on the client's behalf: ticket number 704045.

BritTim · 1 May 2015, 02:15 PM

Support has confirmed that this is an issue isolated to only this single client account.

Their initial attempt to resolve it has not been successful.

BritTim · 4 May 2015, 02:52 AM

For those who are interested in such things, here are some statistics on this issue that the always excellent Bron has now resolved:

Long time enhanced account
Issue reported 3:30 am May 1 (GMT)
First response 4:00 am May 1 (GMT) attempted resolution unsuccessful, referred to developer
Issue resolved 5:30 pm May 3 (GMT)

The issue was related to the beta CardDAV support so, although it was a fairly high impact error, I am not overly critical of the 62 hour time period for a fix.

1 May 2015, 02:15 PM	#2
BritTim The "e" in e-mail Join Date: May 2003 Location: mostly in Thailand Posts: 3,141	Support has confirmed that this is an issue isolated to only this single client account. Their initial attempt to resolve it has not been successful.

4 May 2015, 02:52 AM	#3
BritTim The "e" in e-mail Join Date: May 2003 Location: mostly in Thailand Posts: 3,141	For those who are interested in such things, here are some statistics on this issue that the always excellent Bron has now resolved: Long time enhanced account Issue reported 3:30 am May 1 (GMT) First response 4:00 am May 1 (GMT) attempted resolution unsuccessful, referred to developer Issue resolved 5:30 pm May 3 (GMT) The issue was related to the beta CardDAV support so, although it was a fairly high impact error, I am not overly critical of the 62 hour time period for a fix.