I double checked your suggestions, and I'm certain that the gwia.cfg is
But it's very interesting that you are getting SMTP as a hostname and
I'm getting MAIL as a hostname. I'm telnetting from the internal LAN.
That must be the difference.
Maybe it's a firewall issue. Since I'm NATting public to private
addresses, perhaps it's the firewall that actually relays the hostname.
>>> [log in to unmask] 3/9/2005 4:49:38 PM >>>
When I telnet to "mail.bfafairfax.com" (on port 25) I get this:
220 SMTP service ready
In other words, it's telling me that your hostname is "SMTP". That's
Have you edited your GWIA.cfg by hand? (That's a "no-no", but I do it
all the time.) Are you sure the gwia.cfg file you are looking at is
one GroupWise is actually reading? The working gwia.cfg resides in
sys:system directory not under actual post office file structure.
If you go into Console One and look at the SMTP/MIME settings for the
GWIA object, do you see "mail.bfafairfax.com" in the "Hostname/DNS 'A
Record' Name" field? This field, of course, writes directly to the
gwia.cfg, so it should be okay since you've seen it in the file. But
if, by chance, it has "SMTP" in that field, there's your problem;
what's in the working gwia.cfg file, wherever it is hiding.
I doubt it's that simple a fix, but I'd check there before sleuthing
any further. Let me know what you find and I'll give it some more
Information Technology Director
Montpelier Public Schools
58 Barre Street
Montpelier, VT 05602
[log in to unmask]
>>> [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