550 relay not permitted

v7
mailserver
mail

(River mersey) #1

Hi,

Having just installed nethserver, i find that the letsencrypt certificates work well. Nethserver can send emails to gmail and such like successfully.

however, no emails are being received by nethserver from any source, senders are being given a failed to deliver email stating that the nethserver doesnt accept 550 relays - “550 relay not permitted”. presumably “550” refers to a port or socket number on the nethserver?

yes ive read the docs and cant find any guidance.

does anyone know how to get the nethserver to accept these relays and if doing so would then allow other services to send their email to my users on this nethserver?

many thanks for your time and patince


(Michael Kicks) #2

Usually you have to login for allow relay… on port 587 or 465


(River mersey) #3

logged in or not, nethserver isnt recieving any email from any source - although i CAN send email between users on the same nethserver!


(River mersey) #4

Here’s a slightly different [edited] rejected email reply:

This is the mail system at host mailrelay4-2.pub.mailoutpod1-cph3.one.com.

####################################################################

THIS IS A WARNING ONLY. YOU DO NOT NEED TO RESEND YOUR MESSAGE.

####################################################################

I’m sorry to have to inform you that your message has not yet
been delivered to one or more recipients. It’s attached below.

user@domain.com delayed: domain.com:
400 Could not connect to domain.com:25


(Filippo Carletti) #5

Probably you have to share full real details about your configuration to enable us to help you.
Real domain name to begin.
550 is an internet standard error code used by mail server to report a permanent error.
RFC 5321 should have all the details (https://tools.ietf.org/html/rfc5321).


(River mersey) #6

my real domain is:

https://www.therivermersey.com


(River mersey) #7

Here is what i get from another webmail service:

Error sending message [1708100402050.WM42] from [WM42.inbox.com].

Mail From: jn1057@inbox.com
Rcpt To: postmaster@therivermersey.com
Repeated: <7>
Last Try: <8/11/2017 5:34:59 AM>

The reason of the delivery failure was:

Can not connect to SMTP server <therivermersey.com>.

Here is listed the initial part of the message:

Received: from inbox.com (127.0.0.1:25)
by inbox.com with [InBox.Com SMTP Server]
id <1708100402050.WM42> for postmaster@therivermersey.com from jn1057@inbox.com;
Thu, 10 Aug 2017 04:02:47 -0800
DomainKey-Signature: q=dns; a=rsa-sha1; c=nofws;
d=inbox.com; s=s1;
h=mime-version:date:message-id:from:subject:to:content-type;
b=rM+sLc5gKvmYfWun13LX7tvKKq9ED2BXyNo312idpXqZVIcvEdTtolypPev/iD+SYtOj
SqWnKtJn3qvtz8ttHlGp8abpNVGLTqcVqhptToxlz02XA7ZbIq5A238tDJvv0wm1QawPKY
0XUR6EDHyFxtzsh9BrvrXP78Is1jLFKcI=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; q=dns/txt;
d=inbox.com; s=s1;
h=mime-version:date:message-id:subject:from:to:content-type;
bh=g3zLYH4xKxcPrHOD18z9YfpQcnk/GaJedfustWU5uGs=;
b=hN97DglBMin0FzoJ/0EZsyrDMSj4OxslKmWSGE5ZXNVujUx8Zni3Iraps5YkQtZPUgUr
KFukkeiIzRw8ET+KdwyslHBr+JVHAQisKVxlGB5uuD6WFAN5yELTaQxNhXlqC0eJJXvhtq
QdKCup7a4Ie0Eej6FP/ACLEdQCtIFJu8U=
Mime-Version: 1.0
Date: Thu, 10 Aug 2017 04:02:47 -0800
Message-ID: FA4A931EED5.000010A6jn1057@inbox.com
From: Junk email account jn1057@inbox.com
Subject: test
To: postmaster@therivermersey.com

Back to list << <
> >>

Inbox.com News | Contact Us | Privacy Policy | Terms of Use | Browser Requirements

Copyright © 2017 Inbox.com. All rights reserved.


(River mersey) #8

email account postmaster@therivermersey.com does exist and can send outgoing email!

my problem is that nothing is getting in to the nethserver from any external email services.


(River mersey) #9

Since I published my domain, I’ve had 1248 failed log in attempts!

My Nethserver has been under heavy attack and survived!


(Marc) #10

Fail2ban could be of use there.


(River mersey) #11

As it looks like there is no easy fix to get this 550 relay not permitted situation sorted out, it would seem that i will have to try to fix it by reinstalling nethserver.

Firstly i wanted to try to fix this without reinstalling.
Secondly, i remember that it wasnt entirely straight forward getting the letsencrypt certificates to work so im not looking forward to that either!


(Filippo Carletti) #12

This domain has no MX record, it will never receive email if you don’t fix its DNS records.

$ host -t mx therivermersey.com
therivermersey.com has no MX record

(River mersey) #13

Ahh, ok many thanks. As this ismy first experience of setting up an email server from a bare metal machine, I didn’t really know where to start looking to solve the problem.

When I get the next opportunity, I’ll try to fix the isp records to point MX records to this server. Hopefully it will then work as expected.


(River mersey) #14

Hi again everyone!

Yes i believe Im making progress. MX records problem seems to be fixed. Now im still not recieving emails due to 500 errors as follows:

This is the mail system at host mailrelay3-3.pub.mailoutpod1-cph3.one.com.

I’m sorry to have to inform you that your message could not
be delivered to one or more recipients. It’s attached below.

postmaster@therivermersey.com failed: therivermersey.com:
500 Unable to deliver message to: therivermersey.com


(River mersey) #15

[SOLVED]

Having also sought help from my isp, they advised that I’ve also not set the A record correctly. With all of those things done, all my problems were actually due to my isp misconfigs rather than any nethserver misconfigs!

Many thanks for everyone’s help in putting my on the right track to solving this problem!