FW: government intercepts at NYTimes and Post?

Here's a reply from the Post--seems it was a browser problem...sorry about
the alarm.

Mark Siegmund

----------
> From: webnews <webnews@wpni.com>
> Organization: Washingtonpost.Newsweek Interactive
> Date: Fri, 22 Mar 2002 12:19:41 -0500
> To: Mark Siegmund <Tetworld@highstream.net>
> Subject: Re: government intercepts at NYTimes and Post?
> 
> Dear Mr. Mark Siegmund:
> 
> Thank you for your letter.  I apologize for the difficulty.  We typically see
> this with browsers that might have retained a dated piece of information in
> their cache memory (memory of recently visited sites).  You might consider
> clearing your cache memory.
> 
> To clear your cache:
> 
> Netscape:  Go to Menu Bar > Edit > Preferences > Go to "Navigator" (usually
> the
> default) and click on Clear History in the History section.
> 
> Internet Explorer: Menu bar > View > Internet Options > General > click on
> Clear
> History.
> 
> For AOL's browser (which is actually Internet Explorer) you can: select "My
> AOL"
> from the menu bar, go to Preferences then WWW.   On the Internet Options page
> you would go to the Temporary Internet files and do "Delete Files".  Then go
> down to History and select "Clear History".  This will clear any "stuck"
> pieces
> of information (usually from the past 20 days)  and the Temp files and History
> will begin to accumulate information once again.
> 
> If you have any questions before Clearing your browser's history, you might
> wish
> to consult the browser's help file or your Internet provider for further
> information.
> 
> I hope this helps.
> 
> Sincerely,
> 
> Sarah Abruzzese
> Customer Care
> washingtonpost.com
> email: webnews@wpni.com
> ____________________________________________________________________
> 
> 
> 
> Mark Siegmund wrote:
> 
>> Hello, while trying to access the NYTimes webpage I was intercepted by the
>> following url
>> http://www.whitehouse.gov/adj/N339.nytimes.com/B922384%3babr=!ie%3bsz=720x30
>> 0%3bord=2002.03.22.16.44.07?
>> 
>> the same thing happened when I tried to use the "contact us" feature at the
>> Washington Post website
>> 
>> Please check it out...
>> 
>> Thank,
>> Mark Siegmund
> 
> --
> 
> 
>