Re: Question regarding hotfix 905214

Homework for another server job coming up. On my server, I have the 905214
hotfix and SenderID filtering appears to be working fine. I am just
wondering if there is a problem lurking in the dark where I have not seen it
yet.

Yes, I saw the "hotfix does not replace any other hotfixes" statement and
laughed when I read it. Microsoft has an interesting definition of "replace"
I guess.

Microsoft sure can entertain us. My personal favorite is the one in an
"autodisconnect" article that mentioned a time period of 8,000+ years, then
in parentheses, stated "not tested." I cannot find that reference now.

Gregg Hill



--
----------------

DISCLAIMER WARNING: the information contained in any reply I make is merely
an OPINION, one that I hope you will consider when you make a choice as to
what you will do on your systems or network.

**No recommendation is to be implied by my OPINION.**

There, that should cover it!






"kj [SBS MVP]" <KevinJ.SBS@xxxxxxxxxxxxxxxxxx> wrote in message
news:udfeW1Y%23HHA.1212@xxxxxxxxxxxxxxxxxxxxxxx
Gregg Hill wrote:
KJ,

If I use my high-school algebra, then I get the following.

For SenderID, Exchange SP2 release notes require 905214 = yes, the
905214 SMTP fix is needed for Exchange SenderID = since 914103 fixes
905214, then 914103 is needed by Exchange for SenderID.

I hope someone jumps in here to clarify it!

Gregg Hill

So Greg, are you doing homework or are you having issues? <g>

Here's a twist for your algebraic formulas;

Hotfix replacement information
This hotfix does not replace any other hotfixes.



"kj [SBS MVP]" <KevinJ.SBS@xxxxxxxxxxxxxxxxxx> wrote in message
news:egStBFY%23HHA.5164@xxxxxxxxxxxxxxxxxxxxxxx
Gregg Hill wrote:
KJ,

I agree that the article could be more specific.

However, did you also notice that the Applies To section of 905214
does not even mention Exchange, in spite of the title of the
article? The SMTPSVC.DLL file being replaced is part of IIS in the
C:\WINDOWS\system32\inetsrv folder.

Article 914103 specifically states that it is a fix for the 905214
hotfix, and the 905214 hotfix is listed as required for SenderID in
the Exchange SP2 release notes. How's that for circular reasoning!

So that's what became of the "circular logging" guy!!


In my best judgement, 914103 does not apply to a functioning Exchange
Server.

But hey, maybe we can get Lanwench to give us the straight skinny on
this !


Since the Exchange SMTP Virtual Server is tied to IIS, I think it
would apply.

Any other ideas?

Gregg Hill


"kj [SBS MVP]" <KevinJ.SBS@xxxxxxxxxxxxxxxxxx> wrote in message
news:OfG15jX%23HHA.980@xxxxxxxxxxxxxxxxxxxxxxx
Gregg Hill wrote:
Hi, KJ!

I know that it applies to IIS SMTP, but I thought that Exchange
used the SMTP service. Wouldn't that mean it is needed?

Gregg Hill

Well yes, but Exchange installs SMTP Service Extensions that may or
may not be part of the issues described in the KBs. (I'm on your
side as the KB really lacks suffecient detail)

See the applies to: on 902514 (notice no IIS6.0?)

APPLIES TO
. Microsoft Windows Server 2003, Standard x64 Edition
. Microsoft Windows Server 2003, Enterprise x64 Edition
. Microsoft Windows Server 2003, Enterprise Edition for
Itanium-based Systems
. Microsoft Windows Server 2003, Standard Edition (32-bit x86)
. Microsoft Windows Server 2003, Enterprise Edition (32-bit
x86) . Microsoft Windows Server 2003, Web Edition
. Microsoft Exchange Server 2003 Service Pack 2






"kj [SBS MVP]" <KevinJ.SBS@xxxxxxxxxxxxxxxxxx> wrote in message
news:eXCT7QX%23HHA.1204@xxxxxxxxxxxxxxxxxxxxxxx
Gregg Hill wrote:
Hello!

My server is currently SBS 2003 Premium SP1 with Exchange SP2.

I have a question regarding hotfix 905214. When I read the
Exchange SP2 release notes regarding SenderID at
http://download.microsoft.com/download/f/b/5/fb5c54af-fe5c-48e9-be97-f9e8207325ab/Ex_2003_SP2_RelNotes.htm,
it referred to the http://support.microsoft.com/?kbid=905214
article, which on 8/10/07, had a hotfix that one could request
(which I got and installed), but it now says that the fix is
included in Windows Server 2003 SP2.
There is also another article,
http://support.microsoft.com/kb/914103/en-us, that has a newer
smtpsvc.dll file (6.0.3790.2709) than does hotfix 905214
(6.0.3790.2499). To my knowledge, I have not had any problem
with SenderID, which was enabled after installing hotfix 905214.
Should I be concerned about SenderID not working as designed? I
am not aware of any problems with it.

Gregg Hill

As I read it 914103 is only for IIS/SMTP and not for Exchange.
Just how you'd get there I'm not sure. The article is a little
"light weight". Perhaps if you had exchange and SP2 installed +
905214, then later removed Exchange..???

It sounds like an unpatch for a Service Pack <g>


APPLIES TO
. Microsoft Internet Information Services 6.0



--
/kj

--
/kj

--
/kj

--
/kj



.

Relevant Pages

  • Re: OWA works internally and almost works externally....
    ... The hotfix after SP1 for Exchange can be found from here: ... > Standard Server) that is using port 80 for the default website. ...
    (microsoft.public.windows.server.sbs)
  • Re: Question regarding hotfix 905214
    ... 905214 hotfix and SenderID filtering appears to be working fine. ... I saw the "hotfix does not replace any other hotfixes" statement ... then 914103 is needed by Exchange for SenderID. ... Microsoft Windows Server 2003, Enterprise x64 Edition ...
    (microsoft.public.windows.server.sbs)
  • Re: How can I block email spoofing our domain?
    ... SPF and SenderID allow you to publish, in a DNS TXT ecord, the IP ... addresses (or server names, or a few other mechanisms) of the servers ... that uses the data, and Exchange doesn't. ...
    (microsoft.public.exchange.admin)
  • Re: DST Update Didnt Work
    ... The hotfix say it is for various versions of Outlook. ... server based through Exchange - is the hotfix still required for Outlook? ...
    (microsoft.public.exchange.admin)
  • Re: Event ID 9582
    ... There's no issue with applying the hotfix, ... Exchange service pack like SP2), ... Last week I have installed 4GB of RAM on my Exchange server. ...
    (microsoft.public.exchange.admin)