References: <#DcTVy#> <OIsjY8#> <uw9D4$#>
In-Reply-To: <uw9D4$#>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <#cLp8u$>
Newsgroups: microsoft.public.windows.server.sbs
NNTP-Posting-Host: cpc4-cbly2-0-0-cust406.glfd.cable.ntl.com 86.17.221.151
Lines: 6
Path: num2.nntp.dca.giganews.com!num1.nntp.dca.giganews. com!number.nntp.dca.giganews.com!border2.nntp.dca. giganews.com!nntp.giganews.com!nx02.iad01.newshost ing.com!newshosting.com!newspump.sol.net!news.glor b.com!feeder.erje.net!newsfeed01.sul.t-online.de!newsfeed00.sul.t-online.de!t-online.de!TK2MSFTFEEDS02.phx.gbl!TK2MSFTNGP01.phx. gbl!TK2MSFTNGP06.phx.gbl
Bytes: 1209
X-Original-Lines: 1
Xref: number.nntp.dca.giganews.com microsoft.public.windows.server.sbs:472388
Merv Porter [SBS-MVP] wrote:
> And can the problematic user send mail from OWA?
>
Good call Merv, they can reply via that. It must be a local issue, I'll
recreate the outlook profile and see.
Thanks
Simon
|