"Mike" <> wrote in message
news:3eb44c15-a753-4c7e-8beb-...
On Feb 3, 5:44 am, "Rick Rogers" <r...@mvps.org> wrote:
> Hi Mike,
>
> The error code is typical of a problem on the mail server end, not yours.
> Contact your mail service provider for assistance.
>
> --
> Best of Luck,
>
> Rick Rogers, aka "Nutcase" - Microsoft
> MVPhttp://mvp.support.microsoft.com/
> Windows help -www.rickrogers.org
> My thoughtshttp://rick-mvp.blogspot.com
>
> "Mike" <texan...@hotmail.com> wrote in message
>
> news:774282a3-e85d-490c-9ae3-...
>
> > Running Home Premium & recently I started having mail problems.
> > "Server unexpectedly terminated the connection... socket error 10053
> > error number: 0x800CCC0F"
> > Most of what I've read refers to disabling virus scanning or deleting
> > a digital id, but there is no digital ID & I have disabled virus
> > (Trend Micro 2007) scanning & still no help.
> > Any other suggestions?
Yeah, another fly in the ointment is the size of some of the messages
sent to this company.
I've seen 7 to 10 & even up to 22MB (yes, 22 MEGABYTE) attachments &
then on top of that, they are sent to lists that are made up of
everyone in the company!
And they complain about slow internet speeds, at times - go figure!
I am trying to set up ftp directories that these attachments can be
uploaded to, rather than be sent to everyone's email address, but
we'll see how that goes...
==================
There seem to be technical educational issues at this company. There are
services such as YouSendIt that work very well for exactly this kind of file
transfer.
I know a number of people who send fairly large "industrial audio" files via
YouSendIt and are very happy with its performance. The free "Lite" version
will transfer 100MB files. I've received a few of these files this way, up
to 63 meg, and it's been very fast.
http://www.yousendit.com/
But changing this kind of poor practice needs strong support from the top
levels of the company.
The top management has to approve and communicate a policy limiting email
size and directing staff to send attachments via, say, YouSendIt; only a
link is sent via mail. And the number of recipients can be limited; both
of these restrictions are implemented on the server itself.
The benefit will be that both the mail server and the network itself will
give *much* better response, once they stop just using them incorrectly.
They won't require upgrading, which will save the company significant
amounts, and more actual work will be committed.
HTH
-pk