Topic: email bouncing "Remote host said: 550 No, I don't think you are me"

[brianr]

I had one of my clients servers here for a day to rebuild the system, and had it connected to my broadband as a "server" for a few hours.

Now, after re-installing it this morning at the clients I am getting this:

Hi. This is the qmail-send program at bjsystems.co.uk.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<courses at goldendome dot org dot uk>:
Connected to xxx.xxx.xxx.xxx but sender was rejected.
Remote host said: 550 No, I don't think you're me. Go away.


from it when I try to send an email to it (an email address that I have used 1,000s of times).

SME8 both ends.

Any thoughts?

[CharlieBrady]

You've obfuscated the bounce message, so that makes it hard to definitely diagnose the problem. The error message you have shown is similar to, but not the same as, the message from the check_spamhelo plugin of qpsmtpd. Check what hostname is being used in the "helo" message on the sending host. The receiving host is complaining that the sending host is trying to impersonate it.

In any case, check the qpsmtpd logs carefully. Make them more verbose if you need to.

[CharlieBrady]

I notice that goldendome.org.uk has two different MX hosts. Make sure you know which of those is rejecting the messages (I'd be able to tell you if you hadn't obfuscated the bounce message). Perhaps the backup MX is not doing its job properly. These days backup MX hosts usually aren't required, and it's harder to fight spam when you use them.

[brianr]

I notice that goldendome.org.uk has two different MX hosts. Make sure you know which of those is rejecting the messages (I'd be able to tell you if you hadn't obfuscated the bounce message). Perhaps the backup MX is not doing its job properly. These days backup MX hosts usually aren't required, and it's harder to fight spam when you use them.

Yes, you are right, it was the Mx backup that was rejecting the email, because the SMEServer was not accepting email on port 25.  And the reason for that?  It looks as though when you switch a server from server-gateway to server, then back to Server-Gateway, the IPMASQ stuff gets screweed, all I had to do was go into the server-manager email page, change something (enable IMAPS in this case), then save, and Port 25 got opened.

I'm doing a bug report now....

http://bugs.contribs.org/show_bug.cgi?id=6819

[CharlieBrady]

Yes, you are right, it was the Mx backup that was rejecting the email, ...

Remove it from your domain's DNS.