Re: Some emails not reaching new user; other user cannot open one email

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Dave Nickason [SBS MVP] (gwdibble_at_NOSPAM.frontiernet.net)
Date: 02/10/04


Date: Tue, 10 Feb 2004 12:45:52 -0500

URLSCAN would have been installed as part of the IIS Lockdown tool. It
blocks url's with certain characteristics, and sometimes you can have a
character in an e-mail subject line (such as a ?) that may cause urlscan to
block access to the message. If you have not installed IIS Lockdown, that's
probably not the problem (but you should look into running IIS Lockdown
too). I've been able to delete these corrupted messages by selecting them
and using shift+delete, but they're unrecoverable at that point, which may
not be the result you're seeking.

If you think urlscan may be the issue, see
http://support.microsoft.com/default.aspx?scid=kb;en-us;309508

"Matthew" <thetwamNOSPAM@yahooNOSPAM.com> wrote in message
news:OHgqwu$7DHA.1632@TK2MSFTNGP12.phx.gbl...
> For #1: One mystery cleared up, one remains. I was looking for any rule
> that might be set up, and I noticed that User2 was logged in as User1. No
> wonder she wasn't getting emails addressed to User2!
>
> The remaining mystery for #1 is: why were some emails delayed for a week?
>
> For #2: We started fresh on SBS2K, and although some .pst's were imported
> from a separte NT/Exchange 4 system, the email in question was not. But
> "corrupted" seems an apt description. I tried moving it to a new folder.
I
> cannot forward or reply - when I try it just blinks at me. I've not heard
> of urlscan, I'll look into it.
>
> Many thanks,
>
> Matthew
>
>
> "Dave Nickason [SBS MVP]" <gwdibble@NOSPAM.frontiernet.net> wrote in
message
> news:ecfdEi$7DHA.3052@TK2MSFTNGP09.phx.gbl...
> > For #1, what version of Outlook are you using? Are you sure this is not
a
> > view, filter, rule, or similar issue (or junk mail filtering?). In
> Outlook
> > 2003, the junk mail filter works on internal mail (a bug IMO), and I've
> had
> > it filter legitimate internal messages.
> >
> > For #2, two things come to mind. I had a fair number of messages in
> > different folders that I received while on SBS 4.5. When I upgraded to
> SBS
> > 2000, I could no longer view some of these messages. Apparently they
had
> > been corrupted somehow in the Exchange upgrade. Sometimes moving them
to
> a
> > different folder would make them readable again, or you could try
> forwarding
> > to yourself, or deleting and seeing if it can be read in Deleted Items.
> The
> > second thing is that your OWA issue could be urlscan - if you're
> interested,
> > check the urlscan log or search technet for issues related to urlscan
and
> > Exchange server. There's a KB article about changes that should be made
> to
> > urlscan.ini in an Exchange environment.
> >
> >
> > "Matthew" <thetwamNOSPAM@yahooNOSPAM.com> wrote in message
> > news:%23Ad7vP$7DHA.2796@TK2MSFTNGP09.phx.gbl...
> > > Hello,
> > >
> > > Two odd things that are troubling me, that I don't know how to
> > troubleshoot:
> > >
> > > Small Business Server 2000, Exchange Service Pack 3
> > >
> > > 1) I set up a new user, User1. More than one person says that they
sent
> > > User1 an email but the user did not get it. Most mail does through.
I
> > > tracked a message that did not get through by its message ID, in the
> daily
> > > log in the company.log directory. The log recorded that it got
> delivered,
> > > but it never appeared in User1's mailbox.
> > >
> > > I then set up another new account, User2, and I specify in Delivery
> > Options
> > > of User1 to forward all mail to User2.
> > >
> > > A few days later, User2 is not receiving some emails. However, emails
> > that
> > > were sent to User1 but never received, finally get delivered to User2
> (and
> > > possibly User1 as well), a week later.
> > >
> > > 2) I noticed that I cannot open a specific email in my mailbox. It's
> over
> > a
> > > year old. I click on it and nothing happens. I try to open it via
> OWA,
> > > and I get an HTTP 403 (Forbidden) You are not authorized to view this
> > page.
> > > I do have administrator rights.
> > >
> > > There's nothing too unusual in the log files. Lots of Symantec Mail
> > > Security stopping Novarg/MyDoom. Occasionally we get Warnings (not
> > Errors)
> > > that two objects in the directory have the same proxy.
> > >
> > > This is scaring me, does anyone know what's up?
> > >
> > > Many thanks,
> > >
> > > Matthew
> > >
> > >
> >
> >
>
>



Relevant Pages

  • Re: SBS2K, Exch. 2K, Public Folder error 80040e19
    ... The Exchange organization directory name has not changed nor does it ... I uninstalled URLScan. ... > temporarily uninstall IIS lockdown and URLScan tools, ... > 328659 Error 80040E19 when you try to expand public folders in Exchange ...
    (microsoft.public.windows.server.sbs)
  • Re: OWA: certain emails yield page cannot be displayed
    ... IIS Lockdown and URLscan Configurations in an Exchange Environment ... The URLScan Utility Does Not Allow You to Open Messages in OWA ...
    (microsoft.public.exchange2000.admin)
  • Re: Exchange 2000 and Software Update Services SUS
    ... you'll need to configure URLScan to allow continued access to OWA. ... I would not recommend running SUS on a Domain Controller. ... IIS Lockdown and URLscan Configurations in an Exchange Environment ... : Windows 2000 standard server. ...
    (microsoft.public.inetserver.iis.security)
  • Re: IIS Lockdown
    ... killed FP counters and search forms. ... allowing *.exe extensions in URLscan. ... >files in the install folder, you could edit those and see ... >> I want to run IIS Lockdown before exposing IIS5 server ...
    (microsoft.public.inetserver.iis.security)
  • Re: Trend C/S/M SMB on SBS2003
    ... IIS6 is locked down by default, so you do not need to run IIS Lockdown ... URLScan can run on IIS6 if you wish. ...
    (microsoft.public.windows.server.sbs)