Domain alias relay error

Runbox Chat
1

Starting about 7 hours ago, none of the email for my custom domain has been getting to my account. Senders get a bounce back error: 550 relay not permitted.

I have been using runbox to host my domain email for a couple of months and had no problem. I have several aliases set up and everything has been working fine. I received dozens of emails earlier today. I have not changed any DNS or runbox account settings.

Anyone else experiencing this? I sent a message to support but have had no response and it’s still broken!

I’m heading to bed (western U.S.); I sure hope it’s working when I get up!!

4 Likes
2

It’s fixed now but that was pretty bad, especially for people who run businesses and rely on custom domain emails.

I hope this was a rare occurrance.

3

Glad to hear. Had the same problem here in Europe and was wondering why a [EDIT: particular] conversation did not continue… This explains a lot. Fortunately I have a recovery mechanism for that.

[EDIT2]: To be clear: When I was writing this, everything was running find already. Seemingly in contrast to the other replies downwards vv

1 Like
4

We’re having the same experience here. The support team isn’t responding, and none of the phone numbers we’ve found are being answered.

1 Like
5

Same here … maybe even all customers with email hosting for external domains.
I have 4 domains “down” noct reactivating, different registrars all looking good otherwise.
I gues the routine is broken … have opened support tickets without response for several hours now.

1 Like
6

Same here, last email was 10/12 hours ago, I noticed that my domains were marked as deactivated. When I try to activate them, it goes into pending, but moves back into deactivated.

I haven’t touched any config on runbox or dns in a while so it’s not a change on my end.

I’ve emailed support about 30 minutes ago, lets see how long it takes.

7

I’m getting this error as well.

When I check my Email Hosting Admin the status of my registered domains all read Rejected (Non-existent domain). When I try to reactive them they go into pending before returning to rejected.

I wondered if it’s perhaps because the DNS zone record was set to a legacy string.
v=spf1 ``redirect=spf.runbox.com
instead of
v=spf1 include:spf.runbox.com -all

But it looks like that is returning to rejected again once it’s finished pending.

The whois returns fine. The DKIM is set.

One user got the response
The following organization rejected your message: aibo.runbox.com

(Eastern Australia)

8

Same here in Europe, starting about the same time as mentioned above. No change since then, 550 relay not permitted. Outgoing emails are OK.