Can't send to specific mails, all relevant MX records point.
Posted: Tue Apr 03, 2012 10:03 am
Hi,
I have plesk 10.4.4 latest release + qmail-scanner + qmail + spamassassin + clamav and all that stuff. I'm using CentOS 5.8
Al worked well in plesk 10.3 , since I updated to plesk 10.4.4
It seemed all ok, but I have two different errors with mail that I haven't got before:
1 - 212.49.128.65 does not like recipient.
Remote host said: 550 all relevant MX records point to non-existent hosts
Giving up on 212.49.128.65. ( My MX records are DNS and I didn't change that, that DNS are pointing to my mail server )
2 - with other mail address: 83.243.20.162 does not like recipient.
Remote host said: 554 5.7.1 <hzwart@highco-shopper.com>: Relay access denied
Giving up on 83.243.20.162.
Very strange, Relay access denied ? Y try to send mail to hzwart@highco-shopper.com not to send mail through hzwart@highco-shopper.com ( I use SMTP auth , port 587 avoiding outgoing scanner )
If anyone have a clue to solve that it would be appreciated, but I think this are mistakes from the recievers, not my server, but I'm not sure, as it was working before.
Thanks,
I have plesk 10.4.4 latest release + qmail-scanner + qmail + spamassassin + clamav and all that stuff. I'm using CentOS 5.8
Al worked well in plesk 10.3 , since I updated to plesk 10.4.4
It seemed all ok, but I have two different errors with mail that I haven't got before:
1 - 212.49.128.65 does not like recipient.
Remote host said: 550 all relevant MX records point to non-existent hosts
Giving up on 212.49.128.65. ( My MX records are DNS and I didn't change that, that DNS are pointing to my mail server )
2 - with other mail address: 83.243.20.162 does not like recipient.
Remote host said: 554 5.7.1 <hzwart@highco-shopper.com>: Relay access denied
Giving up on 83.243.20.162.
Very strange, Relay access denied ? Y try to send mail to hzwart@highco-shopper.com not to send mail through hzwart@highco-shopper.com ( I use SMTP auth , port 587 avoiding outgoing scanner )
If anyone have a clue to solve that it would be appreciated, but I think this are mistakes from the recievers, not my server, but I'm not sure, as it was working before.
Thanks,