Issues with Murena email system

Using /e/OS murenacloud
1

When I created my e.email e-mail address, I was planning to make it my main email. After the major Murena cloud outage in 2024/2025 (can’t remember the exact dates), I got very nervous and rolled back to my other email services.

I was planning to wait for a while and see how the Murena Cloud stability progresses, before looking into this subject again.

However, lately I’ve seen some disconcerting things. Like for example, today I had a raft of incoming emails taking between 30 and 60 minutes to arrive in the mailbox. First I thought it might have been a problem at the sender, so sent some test emails from one of my gmail accounts. These messages also took more than 30 minutes to arrive in my Murena mailbox (and when they arrived, their timestamp matched the actual send time, not the receive time, so they didn’t get delayed at the sender’s end).

This makes me very nervous regarding the stability and performance of the Murena Cloud. One might be forgiven to think 30 minutes is not an unreasonable time to wait for an email, but these days a lot of systems use email as a 2FA system (without giving the user an option to change this), which means they send emails valid for 15 or 20 minutes, and if you miss this window, you are unable to login into those systems.

Does the Murena Cloud team have any official information on how things are tracking on this subject, what are the long-term plans, and what availability/reliability stats and SLAs they are working with, these days?

The aforementioned Murena Cloud major outage shook many users’ confidence in this service, putting Murena on the back foot, in an already highly competitive market (there are MANY providers of such services these days).

Without a very proactive approach on fast quality uplift, as well as increased public visibility and image improvement, Murena risks of becoming an “also ran”, which will always be linked to their (dare I say) disastrous outage I have already mentioned.

3 Likes
2

Interesting coincidence, I have also remarked this problem. Hence, I have taken a look at the mail headers of received mails:

  • The delay is caused internally: The mails seem to arrive at the Murena servers within a couple of seconds, but the forwarding to the mail server seems to take 45 minutes (or longer).
  • This problem was not present on Tuesday, August 4, where a friend’s mail arrived at the Murena mail server within seconds (according to the mail headers).

This problem also happened a year ago or so (and was fixed).

@Manoj: Can you forward this problem to the Murena infrastructure team? As I am a paying customer, should I also write an email to support?
BTW, could the Murena infrastructure team already take a look at the frequent 502 errors of push.murena.com?

3 Likes
3

As a paying customer you should send a mail to helpdesk to check if there are other issues with your account.

In parallel I have informed the infra team to check.

4 Likes
4

As of now, the problem seems to be fixed: Two test mails that I have sent from my GMX account have almost instantaneously arrived in the Murena inbox.
@centaurus : Has the problem also been fixed for you?

5

The problem seems to have been solved now, but the questions above still remain…

6

A fix is being pushed along with the next release.

2 Likes
7

Excellent, will additional information about the server update etc. be available? The questions by @centaurus should be addressed.
cc @GaelDuval

8

The servers were facing some network related issues which causes slowness in response. Requests were getting rejected. The infra team check and restarted the servers which restored normal services. The teams have been requested to maintain constant vigil to mitigate such occurrences in future.

2 Likes
9

Thank you for forwarding the issues, I hope a proper monitoring will be installed. BTW, push.murena.com sometimes still has 502 errors, I hope that the next update will fix this.

10

I am having problems in this regard too. Not every day but still frequently.

At times it is taking a long time to receive messages and also for messages to send, which is very frustrating!

I received an email today at around 12.30pm, that according to the header had been sent at 9am. I also ‘sent’ an email at 12.28pm and its still sitting in my outbox at 12.51pm.

Additionally, as op says, it becomes impossible to log in to any site that requires 2FA as the email takes too long to arrive.

Most annoyingly, I have been replacing an old email address with this one over several months, now I’m wondering if I’ve made a mistake doing so!

Added to above, I’ve also just received this alert. No idea how to resolve this, can anyone more techy than me help please?

1000004383
10000043831116×498 46 KB

1 Like
11

Today no email reception :hot_face:

3 Likes
12

I can confirm this problem.

I have just sent an email to Murena support: I have to emphasize that I am a strong supporter of Murena and a paying customer. However, the reliability has to be improved so that I can endorse it even more.

Dear Murena Support,

I am a paying Murena.io customer, and I really like the ecosystem that has been established so far.

Nevertheless, there are several concerns:

  • I am not sure whether a proper post-mortem analysis of the long NextCloud storage outage of murena.io has ever been published.
  • For at least the third time, the emails at murena.io arrive with a considerable delay. According to the mail headers, this problem is caused by a long waiting time of the mails on a Murena server.
  • push.murena.com is the backbone of the UnifiedPush infrastructure, but has had performance issues for several weeks now. This issue has been raised in Ticket#99108121.
  • Server certificates were no longer valid, which was several times remarked by users in the community forum.
  • The installed server software is not always up-to-date. This may not be an issue (for instance. murena.io uses NextCloud 32, but without known security vulnerabilities), but sometimes, it really is (push.murena.com openly declares that its reverse proxy is an nginx 1.28, which has known security vulnerabilities).

I think that the infrastructure team is already working hard and doing their best.

Still, I have several suggestions:

  • After each solved problem, a short statement should be published: What was the problem, how was it solved, how will this be prevented in the future? Manoj is an excellent community manager, and he always forwards problems raised in the community forum to the infrastructure team. However, there should be an official response in the dedicated forum section.
  • If one performance or reliability problem has been fixed, the corresponding metrics should automatically be monitored in the future so that any problems are directly remarked by the infrastructure team.
  • Please publish your current performance and uptime metrics. Please let the community also know the corresponding requirements that you want to achieve, and also how you want to achieve them.

Best regards, …

cc @Manoj @GaelDuval

EDIT: My message has received Ticket#99109708.

EDIT 2: Two test mails arrived with a delay of 2.5h and almost 3h.

6 Likes
13

The issue has been forwarded to the infra team to check. It being the weekend the response is getting delayed. Following up on it with the team.

Will share an update on the forum, on the reasons for the issue once it is resolved.

3 Likes
14

Hi, I can say that I’m also experiencing this problem; emails arrive 30 or 40 minutes late.

1 Like
15

Unfortunetaly, so do I.

2 Likes
16

Timestamps in mail header indicate delay of about 75 minutes. Not good for a login code that has 15 minute validity!
This has been going on for at least a few days.

Sending from my murena account to my other account is almost instant.

Received: from mail01.ecloud.global
	by mail01.ecloud.global with LMTP
	id +BH5LvfEimoKyTMAIbUGlA
	(envelope-from <bounce+c541e0.bbd063b-me=e.email@core.patreon.com>)
	for <me@e.email>; Sun, 23 Aug 2026 10:01:27 +0000
Received: from 225-154.static.patreon.com (225-154.static.patreon.com [159.135.225.154])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by mail01.ecloud.global (Postfix) with UTF8SMTPS id 534FE34850A4
	for <me@e.email>; Sun, 23 Aug 2026 08:46:47 +0000 (UTC)

Edit: another test email took 8 seconds to get from my mail provider to mail01.ecloud.global then almost exactly one hour to move from mail01.ecloud.global to mail01.ecloud.global (yes, the same host)

3 Likes
17

I would say personally its more like a few weeks than a few days!

1 Like
18

last few / times I saw an email delay I guessed it to be a misconfigured rspamd graylisting module.
The +75min lmtp timestamp is dovecot, so delay is all whatever postfix plumbing is up to.

19

The issue with the delay has been resolved. Will check with the team on the reason and update.

5 Likes
20

I have had a honest mail conversation with Murena support. If I can link the resulting GitLab issues, I will post them here.