Topic: [ EMAIL ] QMAIL - Remote_host_said:_553_Bad_ip_syntax

[mterrasson]

Hello !

First of all, thank you all for your amazing work on SME Server !

Context :

[INTERNET] ----- [ROUTER/FIREWALL] ------ [LAN]
                                                               |
                                                               |
                                             [SME 1]----[PCs]----[SME 2]
SME 1 is a domain controler and a file server (domain is something.local)
SME 1 is backuped to SME 2 using rsync, the script also send an email with log to some external email adresses.

PROBLEM :
My problem is that the ISP smtp is using port 587 and authentification. I changed that via server-manager (using console) ( smtp.myisp.com:587, and enabling auth with an account that I know is working)

The router blocks port 25 trafic.

when I send email using mail command, i've got this error in /var/log/qmail/current :

Code: [Select]

@400000004e88347e016202f4 delivery 2158439: failure: Connected_to_127.0.0.1_but_sender_was_rejected./Remote_host_said:_553_Bad_ip_syntax/
I thought my problem was that the mail was send from root@mydomain.local to an external address and SME smerver did not like that.
So i used sendmail with a file including from: to: subject: . But the problem was still here.

I've search the internet and contribs.org looking for any solutionse but I found nothiing relating to 553 bad ip adress for Qmail.

I'll be glad to here any suggestion of any of you
If you need more informations, just ask !

Regards,

[janet]

mterrasson

Try searching on
Remote host said: 553 Bad ip syntax
there are lot's of search results

I thought my problem was that the mail was send from root@mydomain.local to an external address and SME smerver did not like that.

You would be better to use a real domain name that does resolve externally, that way you will not have other unusual problems.
I'd suggest changing the main domain name on sme1 to
myrealdomain.com

ie drop the .local as that is Windows parlance and does not work well with sme server.

Your message may be getting rejected due to it being considered as spam or coming from an unresolvable server domain name.

[mterrasson]

You would be better to use a real domain name that does resolve externally, that way you will not have other unusual problems.
I'd suggest changing the main domain name on sme1 to
myrealdomain.com

ie drop the .local as that is Windows parlance and does not work well with sme server.

Your message may be getting rejected due to it being considered as spam or coming from an unresolvable server domain name.

The 553 bad ip syntax ran off ! I just change the smtp configuration using command line

Code: [Select]

config set SMTPSmartHost "smtp.myisp.com:587"
The new error code is realated to the domain problem.

I never had to change a domain.local to a domain.com on SME server. All my SME servers installed as a domain controler are related to a real domain except this one.

If I change my local domain name, what would be the consequences for my LAN ?

Thank you for your quick answer,
Regards

[janet]

mterrasson

If I change my local domain name, what would be the consequences for my LAN ?

It is OK to do so.
The impact on your LAN is something you need to assess eg do your workstations have URL's that resolve to the sme1 server ?
If so they would need to be amended.

[mterrasson]

Thank you Mary for your help, I owe you one

Best regards,

[CharlieBrady]

The 553 bad ip syntax ran off !

What do you mean "ran off"? Do you mean you don't see that any more?

If so, that would be that you had an invalid  entry for SMTPSmartHost and you changed it to something which is valid.

Out of interest, what did you formerly have for SMTPSmartHost? If you don't remember, you can find out by typing:

cat /var/log/messages.* | grep SMTPSmartHost=

Knowing what you had previously might help if somebody else has a "Bad ip syntax" problem.

[CharlieBrady]

The new error code is realated to the domain problem.

What new error code? Are you saying that you still had a problem after changing SMTPSmartHost, but the new problem was different, with a different error message? If so, please tell us what that error message was.

[mterrasson]

I've no access to the SME ATM, but i will answer you in a few hours.