Mr
Thu Jun 23 10:23:34 CDT 2005
I got it working... thank you.
I was instructed to make the changes in the folder of: C:\Program
Files\Exchsrvr\exchweb\6.5.6944.0
But in my exchange I have C:\Program Files\Exchsrvr\exchweb\6.5.6944.0 and a
folder called C:\Program Files\Exchsrvr\exchweb\6.5.7226.0
It seems that the folder "C:\Program Files\Exchsrvr\exchweb\6.5.7226.0" is
the active folder and was created after my SP update for exchange.
"Al Mulnick" <amulnick_No_SPAM@ncDOTrr.com> wrote in message
news:ueHtxo$dFHA.1456@TK2MSFTNGP15.phx.gbl...
> Actually they did. What they likely figured is that nobody would really
> want their end users to look through miles of headers to figure out if
> every one of the 700 + messages they received that day were legit and
> likely assumed that most users wouldn't know the names of the legit
> servers anyway.
>
> Instead, they made it more noticeable in the from line of the message
> header by putting the users SMTP address next to the name if it did not
> originate locally to the system. So if you send via SMTP, you'll see it
> with the <name>[smtp:address@here.com] format vs. friendly name you see in
> the GAL.
>
> I'm interested in knowing a user population that looks through every
> header before figuring something is legit vs. using something like PKI to
> ensure the legitimacy of emails. That's also possible with OWA 2003 FWIW.
>
> Thoughts?
>
> "Mr. Backup" <backup@yahoo.com> wrote in message
> news:erp4Bk$dFHA.3712@TK2MSFTNGP09.phx.gbl...
>> Thank you...
>>
>>
>>
>> Well I have tested it and that didn't work.
>>
>> I was looking for an in/house method of doing this, perhaps some
>>
>> registry setting that we left turned off. I can't believe the
>>
>> capability isn't there as a default.
>>
>>
>>
>> I guess the programmers at M$ never thought someone out there in this
>>
>> friendly world would ever dare to send a forged email message,
>>
>> masquerading as another person.
>>
>>
>
>