Mta settings Nodeworx

[cape]

Hi

Dns stuff tells me:

WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). If your mailserver sends out E-mail using this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam software. This is also a technical violation of RFC821 (http://www.dnsstuff.com/pages/rfc821.htm) 4.3 (and RFC2821 (http://www.dnsstuff.com/tools/rfc.ch?detail=2821) 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server. Note that this one test may use a cached DNS record.

domainName.com claims to be invalid hostname 'InterWorx-CP':
220 InterWorx-CP SMTP Server ESMTP

Now how do i change the settings under nodeworx to fixx this issue?

Thx

[NEXCESS.NET (Greg)]

You can change this by editing:

/var/qmail/control/smtpgreeting

and then running:

svc -t /service/smtp

[NEXCESS.NET (Greg)]

Oh..and you can also change it in NodeWorx on the System Services > Mail Server > MTA Settings page. Top right corner.

[cape]

Oh..and you can also change it in NodeWorx on the System Services > Mail Server > MTA Settings page. Top right corner.


When i am trying to change this under Nodeworx i get;

» Invalid blacklist e-mail : .*\
» Invalid blacklist e-mail : @.*
» Invalid blacklist e-mail : !.*@.*\..*
» Invalid blacklist e-mail : .*%.*


What should i type in that box?

[IWorx-Socheat]

Is this a 2.x box? If so, this is a known bug on the MTA settings page and is fixed in 3.0. The instructions Greg gave you for changing the greeting from the command line should still work.

[cape]

Is this a 2.x box? If so, this is a known bug on the MTA settings page and is fixed in 3.0. The instructions Greg gave you for changing the greeting from the command line should still work.

Yes it's 2.1.3

What should be proper greeting?

[IWorx-Socheat]

According to that warning, it should be a valid hostname that points back to the same server.

[cape]

did

vi smtpgreeting got empty file?

[Justec]

/var/qmail/control/smtpgreeting should not be empty.

The smtpgreeting should contain the host name (probably whatever you have under "Mail Server Hostname (FQDN):")

[cape]

Mine is totaly empty unless " vi " it's not showing me what file contains:)

[Justec]

Well then you should just type it in manually there. Maybe nodeworx blanked the file when you tried to update it earlier?

[cape]

You can change this by editing:

/var/qmail/control/smtpgreeting

and then running:

svc -t /service/smtp

Hey Greg,

Please let me know what should i type in smtpgreeting file mine is totaly empty.

[NEXCESS.NET (Greg)]

a valid hostname that points back to the same server

[Justec]

In mine I have:
mail.justechnology.com Qmail

and it passed all the test on the dns website tester thingy.

[cape]

In mine I have:
mail.justechnology.com Qmailand it passed all the test on the dns website tester thingy.
i did exact same thing added A record for mail.mydomainname.com Qmail It's still screaming at me in DNS thingy:)

[Justec]

There are two things you need to do.

1) Make the DNS A record to point to the IP of the server with mail.domainname.com
2) Change the hostname to mail.domainname.com Qmail Server or Whatever

Are you still getting the same error as the 1st post of this thread?

[cape]

i did all above maybe i have to wait or something?

[Lightfoot]

domainName.com claims to be invalid hostname 'InterWorx-CP':
220 InterWorx-CP SMTP Server ESMTP

What is dns stuff telling you this is now after changing your hostname? Does it still say InterWorx-CP or does it say your hostname?

[cape]

What is dns stuff telling you this is now after changing your hostname? Does it still say InterWorx-CP or does it say your hostname?


now i get domainname.com claims to be invalid hostname ' ':
220 ESMTP

[Lightfoot]

now i get domainname.com claims to be invalid hostname ' ':
220 ESMTP

Hmmm... well when I setup my MTA hostname through nodeworx I received those same errors, so I just removed the lines in the blacklist input fields and it worked then. Not sure if that's something you want to try, but changing the /var/qmail/control/smtpgreeting file to reflect your hostname and restarting the smtp service should work. That file should not stay blank after it is saved.

[Justec]

and restarting the smtp service should work.Forgot to mention that part, maybe that was the problem?

[cape]

i change smtgreeting file i am able to put and save anything i want there now i have mail.domainname.com Qmail


removing blacklist not sure if i want to.

maybe i should mention that i just moved the domain from shared to vps and having problems with transferring my domain. I am using my isp ns servers but where i am dns times out. I did this last night.

I had to create A, MX, CNAME records plus point domain to new ns servers.
It's very strange now all my googleadsense layout is broken up. Domain is very slow to pull out, many times times out one me.

Maybe that's the reason why i am having all this issues

[Lightfoot]

Well I think if DNS Report is showing your nameservers at the new location (somewhere toward the top of the report) it will be reading the information setup on that server. Try restarting SMTP and see if that works.

[127.0.0.1]

ok...i'm following what everyone is saying (i think!)...but here's a curve ball:

my box is host.myserver.com and qmail is setup and smtpgreeting reports host.myserver.com

i added an IP-based site newdomain.com

when i run dnsreport for newdomain.com the mailserver shows as host.myserver.com instead of mail.newdomain.com and flags with the standard warning:

"WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). If your mailserver sends out E-mail using this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam software. This is also a technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server. Note that this one test may use a cached DNS record.

mail.newdomain.com claims to be host host.myserver.com [but that host is at 12.34.56.78 (may be cached), not 23.45.67.89]. <br />"

so, here are my dns records for newdomain.com:

newdomain.com A 23.45.67.89 43200
ftp.newdomain.com A 23.45.67.89 43200
mail.newdomain.com A 23.45.67.89 43200
www.newdomain.com A 23.45.67.89 21001
newdomain.com NS ns1.myserver.com 43200
newdomain.com NS ns2.myserver.com 43200
mail.newdomain.com MX 10 43200
newdomain.com SOA Edit SOA Properties 43200
newdomain.com TXT v=spf1 a mx ~all 43200

so, the question is this...how do i get rid of the dnsreport flag? if i need to add an "A" record to newdomain.com's dns records, what should it be exactly?

thx in advance,
john

[127.0.0.1]

on a whim, i went ahead and added the following "A" record on newdomain.com and got rid of the dnsreport mailserver flag:

mail.newdomain.com A 12.34.56.78

where 12.34.56.78 is the main IP of the server

john