It appears that the SMTP proxy on our firewall is hiding the hostname of
the email server and responding with the SMTP answer. I've gotten a
response back from the firewall tech support. Their SMTP engineer claims
that this is done for security reasons, and it is not a violation of
RFC. They claim that, if DNS is properly set up it, the hostname is
irrelevant. Of course surfglobal.net is telling me otherwise.
So...I'm waiting for Green Mountain Access tech support to help me
verify that our DNS is correct. If it is, I guess I'll have to be
prepared to hurl myself at two large corporations - a bloody sacrifice
to the technology gods.
Thank you, everyone, for your help with this. You certainly got me
going in the right direction, with the right questions to ask.
Now, I think I need a lawyer.
>>> [log in to unmask] 3/10/2005 9:18:55 AM >>>
You said that when you telnet you get "220 mail <some Groupwise stuff>
ready". This is different than what we are getting from the outside.
The message we get is "220 SMTP service ready" It looks like there is
no host name here at all so others think that SMTP is the host. But
more importantly it does not respond from the outside as even being a
GroupWise system (it should say the version of GroupWise here - each
mail handler has a different message here but uses the same commands
process mail). Is the external address 126.96.36.199? Does the NAT go
to the right internal address? Are you using a spam filter or
your mail to your isp (you should be able to tell if you have a
/mh-<ipaddress> in your gwia.cfg)?
>>> [log in to unmask] 3/9/2005 3:56:21 PM >>>
Can any of you Groupwise administrators help with a problem that I'm
Our Groupwise 6.5 sp2 server appears to be responding to other email
servers with the wrong hostname. Because of this, the surfglobal.net
email server rejects all mail from our domain. It thinks that it is
The error report under the properties of the rejected email gives the
following error message:
504 <mail>: Helo command rejected: need fully-qualified hostname
A report on our domain from www.dnsreport.com gives the following
WARNING: One or more of your mailservers is claiming to be a host
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). This probably
cause any harm, but is a technical violation of RFC821 4.3 (and
4.3.1). Note that the hostname given in the SMTP greeting should have
A record pointing back to the same server.
mail.bfafairfax.com claims to be invalid hostname 'SMTP': 220 SMTP
Our server name is mail.bfafairfax.com. When I telnet in to
mail.bfafairfax.com on port 25, it responds:
220 mail <some Groupwise stuff> ready.
Should it respond:
220 mail.bfafairfax.com <Groupwise stuff> ready
instead of just mail?
My host and hostname files on the Groupwise server reflect
mail.bfafairfax.com and its private IP address. My gwia.cfg file
Our Groupwise server sits in the DMZ behind our firewall. It has a
private IP which has a 1-to-1 NAT to the public IP.
I just can't figure out what is happening.
Thanks in advance for any help you might be able to offer.
Bellows Free Academy
This e-mail may contain information protected under the Family
Educational Rights and Privacy Act (FERPA). If this e-mail contains
student information and you are not entitled to access such information
under FERPA, please notify the sender. Federal regulations require that
you destroy this e-mail without reviewing it and you may not forward it