Login issue faced on our Business Email Service Posted by on 14 November 2016 02:06 PM
|
|
[Update:14/11/2016: 8:30 PM IST] The maintenance on passive replica server has been completed successfully. We made this server as primary and started services successfully. Now you can access emails without any issues via webmail interface and email clients. You shouldn't face any issue while sending or receiving emails. We have a large number of emails in email queue. It is taking time to process emails in queue. You will receive all emails sent to the affected accounts during this downtime once the mail queue is processed. We will update this thread once the mail queue is processed. We are sorry for the inconvenience caused. We have a large number of emails in email queue. It is taking time to process emails in queue. You will receive all emails sent to the affected accounts during this downtime once the mail queue is processed. We will update this thread once the mail queue is processed. We are sorry for the inconvenience caused. We will update this thread once the mail queue is processed. We are sorry for the inconvenience caused. ==================================================================== [Update:14/11/2016: 5:15 PM IST] We observed a file system error on one of our mail storage servers. We attempted to failover to a passive replica but the error had already been replicated. We then took the storage pair out of production in order to restore consistency to the filesystem. We have started this maintenance but due to a large amount of data on the server we expect this to take a few more hours. =========================================================================== We are currently facing an issue with the webmail interface of our Business mail service, clients may encounter the error “An error occurred inside the server which prevented it from fulfilling the request. (LGI-0003)” while opening their account via webmail interface or while connecting through their email clients. Our senior administrators are already working on this issue and are trying to fix this as soon as possible. | |
|