outbound mail address

I'm being told that my exchange server is sending mail with a header that
shows my server as servername.mydomain.int rather than
servername.mydomain.com and that some servers won't accept mail with this
header? How do I correct this?

Bharat
Tue Feb 06 21:29:54 CST 2007

(Assuming there's just one Exchange server) - go to SMTP Virtual Server
properties | Delivery tab | Advanced - in "Fully-qualified domain name:"
field enter servername.mydomain.com.
--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
exchangepedia.com/blog
----------------------------------------------


"Don Powell" <DonPowell@discussions.microsoft.com> wrote in message
news:180FD696-2E9D-4F10-8E83-4DF17C56EA8E@microsoft.com...
> I'm being told that my exchange server is sending mail with a header that
> shows my server as servername.mydomain.int rather than
> servername.mydomain.com and that some servers won't accept mail with this
> header? How do I correct this?

DonPowell
Tue Feb 06 22:22:01 CST 2007

Actually, it's two. Does that change the answer?

"Bharat Suneja [MVP]" wrote:

> (Assuming there's just one Exchange server) - go to SMTP Virtual Server
> properties | Delivery tab | Advanced - in "Fully-qualified domain name:"
> field enter servername.mydomain.com.
> --
> Bharat Suneja
> MVP - Exchange
> www.zenprise.com
> NEW blog location:
> exchangepedia.com/blog
> ----------------------------------------------
>
>
> "Don Powell" <DonPowell@discussions.microsoft.com> wrote in message
> news:180FD696-2E9D-4F10-8E83-4DF17C56EA8E@microsoft.com...
> > I'm being told that my exchange server is sending mail with a header that
> > shows my server as servername.mydomain.int rather than
> > servername.mydomain.com and that some servers won't accept mail with this
> > header? How do I correct this?
>
>
>

Bharat
Tue Feb 06 23:10:37 CST 2007

Yes it does - if you have two Exchange servers, and a SMTP Connector for
address space *, check which SMTP virtual server is the bridgehead on the
Connector and make the change on that SMTP VS. If you don't have a SMTP
Connector for *, you would have to create one.
--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
exchangepedia.com/blog
----------------------------------------------


"Don Powell" <DonPowell@discussions.microsoft.com> wrote in message
news:77DECD78-BA71-45C3-B692-6B31950CA6B3@microsoft.com...
> Actually, it's two. Does that change the answer?
>
> "Bharat Suneja [MVP]" wrote:
>
>> (Assuming there's just one Exchange server) - go to SMTP Virtual Server
>> properties | Delivery tab | Advanced - in "Fully-qualified domain name:"
>> field enter servername.mydomain.com.
>> --
>> Bharat Suneja
>> MVP - Exchange
>> www.zenprise.com
>> NEW blog location:
>> exchangepedia.com/blog
>> ----------------------------------------------
>>
>>
>> "Don Powell" <DonPowell@discussions.microsoft.com> wrote in message
>> news:180FD696-2E9D-4F10-8E83-4DF17C56EA8E@microsoft.com...
>> > I'm being told that my exchange server is sending mail with a header
>> > that
>> > shows my server as servername.mydomain.int rather than
>> > servername.mydomain.com and that some servers won't accept mail with
>> > this
>> > header? How do I correct this?
>>
>>
>>

DonPowell
Wed Feb 07 05:58:00 CST 2007

Oooh, I have 1 SMTP connector (with address space *) which includes both
servers as local bridgeheads so they both send out the mail for their side
but my inbound mail only comes into one of them, which routes inbound mail to
the second server. Is that OK and, if so, do I just change the SMTP Virtual
Server address on the one that is actually recieving all of the mail?

Thanks

"Bharat Suneja [MVP]" wrote:

> Yes it does - if you have two Exchange servers, and a SMTP Connector for
> address space *, check which SMTP virtual server is the bridgehead on the
> Connector and make the change on that SMTP VS. If you don't have a SMTP
> Connector for *, you would have to create one.
> --
> Bharat Suneja
> MVP - Exchange
> www.zenprise.com
> NEW blog location:
> exchangepedia.com/blog
> ----------------------------------------------
>
>
> "Don Powell" <DonPowell@discussions.microsoft.com> wrote in message
> news:77DECD78-BA71-45C3-B692-6B31950CA6B3@microsoft.com...
> > Actually, it's two. Does that change the answer?
> >
> > "Bharat Suneja [MVP]" wrote:
> >
> >> (Assuming there's just one Exchange server) - go to SMTP Virtual Server
> >> properties | Delivery tab | Advanced - in "Fully-qualified domain name:"
> >> field enter servername.mydomain.com.
> >> --
> >> Bharat Suneja
> >> MVP - Exchange
> >> www.zenprise.com
> >> NEW blog location:
> >> exchangepedia.com/blog
> >> ----------------------------------------------
> >>
> >>
> >> "Don Powell" <DonPowell@discussions.microsoft.com> wrote in message
> >> news:180FD696-2E9D-4F10-8E83-4DF17C56EA8E@microsoft.com...
> >> > I'm being told that my exchange server is sending mail with a header
> >> > that
> >> > shows my server as servername.mydomain.int rather than
> >> > servername.mydomain.com and that some servers won't accept mail with
> >> > this
> >> > header? How do I correct this?
> >>
> >>
> >>
>
>
>

DonPowell
Wed Feb 07 06:04:00 CST 2007

It just dawned on me that if I only change the address on the mail Virtual
SMTP Server then any mail being sent out by the second one would still have
an address of server.domain.int so I'm thinking that I need to change it on
both, no?

"Bharat Suneja [MVP]" wrote:

> Yes it does - if you have two Exchange servers, and a SMTP Connector for
> address space *, check which SMTP virtual server is the bridgehead on the
> Connector and make the change on that SMTP VS. If you don't have a SMTP
> Connector for *, you would have to create one.
> --
> Bharat Suneja
> MVP - Exchange
> www.zenprise.com
> NEW blog location:
> exchangepedia.com/blog
> ----------------------------------------------
>
>
> "Don Powell" <DonPowell@discussions.microsoft.com> wrote in message
> news:77DECD78-BA71-45C3-B692-6B31950CA6B3@microsoft.com...
> > Actually, it's two. Does that change the answer?
> >
> > "Bharat Suneja [MVP]" wrote:
> >
> >> (Assuming there's just one Exchange server) - go to SMTP Virtual Server
> >> properties | Delivery tab | Advanced - in "Fully-qualified domain name:"
> >> field enter servername.mydomain.com.
> >> --
> >> Bharat Suneja
> >> MVP - Exchange
> >> www.zenprise.com
> >> NEW blog location:
> >> exchangepedia.com/blog
> >> ----------------------------------------------
> >>
> >>
> >> "Don Powell" <DonPowell@discussions.microsoft.com> wrote in message
> >> news:180FD696-2E9D-4F10-8E83-4DF17C56EA8E@microsoft.com...
> >> > I'm being told that my exchange server is sending mail with a header
> >> > that
> >> > shows my server as servername.mydomain.int rather than
> >> > servername.mydomain.com and that some servers won't accept mail with
> >> > this
> >> > header? How do I correct this?
> >>
> >>
> >>
>
>
>

mpriem
Wed Feb 07 08:43:30 CST 2007

!!!!!! Do not change the FQDN on the virtual server !!!!!!

http://msexchangeteam.com/archive/2005/02/25/380481.aspx

mpriem
Wed Feb 07 09:01:23 CST 2007


It is not a header that other servers do not accept. During the ehlo/
helo command a smtp server specifies its FQDN
A lot of servers do a 'HELO lookup' where the FQDN is varified with
DNS. In a lot of cased the message is dropped.
Some servers also use a reverse lookup to check your ip with dns to
match it with your FQDN. When this does not match you will recieve a
higher possible spam rating. No smtp server will immediately block it
as a lot of mailservers do not have a PTR record in dns, which is used
for reversed lookups.

Unfortunately you cannot change the FQDN anywhere else as on the
Virtual server. Please read the link I send in my previous reply if
you want to change it.
One of the main complications is internal routing. The FQDN on the
Exchange server MUST be verified in DNS to your internal addresses. (I
think you use NAT for outside connections). You can full your servers
by adding the FQDN in the hosts file, but a better solution would be
to use a smart-host (like the smtp server of your ISP or a postfix
server)

DonPowell
Wed Feb 07 09:43:00 CST 2007

Just read it. So I really want my email headers to show mail as coming from
my internal domain name?

"mpriem" wrote:

> !!!!!! Do not change the FQDN on the virtual server !!!!!!
>
> http://msexchangeteam.com/archive/2005/02/25/380481.aspx
>
>

Bharat
Wed Feb 07 10:09:14 CST 2007

:)

- Changing fqdn on gateway servers (bridgeheads) is quite common in similar
circumstances, and doesn't break anything.
- Message-ID doesn't change in headers, but that doesn't impact message
routing
- Before you proceed, understand the reason why you're doing this. Are
specific remote hosts dropping messages because of this?

- From Scott's post on the team blog:
"Note: we loosened this requirement in Exchange 2003 because we now first
attempt to bypass DNS resolution and try to first use the specified IP
address of the virtual server. Clearly, however, we must fall back to DNS
if the VSI is set to "All Unassigned.""

and "...with the exception of the gateway server scenario, I generally
recommend staying away from modifying or adding SMTP virtual servers,"



--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
exchangepedia.com/blog
----------------------------------------------


"mpriem" <spam@mpriem.com> wrote in message
news:1170859410.497696.184990@a75g2000cwd.googlegroups.com...
> !!!!!! Do not change the FQDN on the virtual server !!!!!!
>
> http://msexchangeteam.com/archive/2005/02/25/380481.aspx
>

mpriem
Wed Feb 07 11:00:56 CST 2007

So if I understand correctly setting the specified IP address will
resolve the internal routing issue when modifying the FQDN on a
virtual server?

Jamestechman
Fri Mar 09 16:09:22 CST 2007

Even if you were to do this on your front end servers, the headers
will still show the history of the message showing the internal name
of your backend server. So unless you change all your servers it
doesn't really serve to just change your FE if your intent is to hide.
Hiding doesn't really serve any purpose and changing your BE servers
could affect internal routing as the article mentions. Yeah, it's
annoying many orgs will block just because you fail helo lookups. RFC
states that you should not block based soley on this but people will
not follow all RFC standards. One option you can do is register your
internal domain name but that can open up a can of worms in itself.


James Chong (MVP)
MCSE | M+, S+, MCTS, Security+
msexchangetips.blogspot.com





On Feb 6, 9:51 pm, Don Powell <DonPow...@discussions.microsoft.com>
wrote:
> I'm being told that my exchange server is sending mail with a header that
> shows my server as servername.mydomain.int rather than
> servername.mydomain.com and that some servers won't accept mail with this
> header? How do I correct this?