This has nothing to do with server timeouts - it has everything to do with AV that scans incoming/outgoing email. Disable it and things should return to normal. You may need to uninstall and reinstall without the mail scanning option to completely cure the issue.
--
Milly Staples [MVP - Outlook]
Post all replies to the group to keep the discussion intact.
After furious head scratching, MarkHays asked:
| We ran into the same problem with Outlook 2007 / 2003 / Express. It
| typically occurs with larger file attachments. If the "server
| timeout" value in Outlook is set to the default, the 'send' function
| well enter a repetitive loop if the process is delayed, e.g. by a
| slow response from the email server, a poor wireless connection, a
| large file attachment, a large distro list or the time required for
| an AV scan.
|
| One of our users, for example, sent an email with a 4Mb attachment --
| Outlook 2007 delivered 42 copies to the recipient, filling up his
| email account. Needless to say, the client wasn't happy. Then 20
| "rejected" copies were returned to her email box -- which also filled
| up!
|
| The best workaround is to set the 'server timeout' to 5+ minutes if
| you have a fast connection -- or more if the connection is slow, e.g.
| for portables used by salespeople, with shaky airport WiFi links. To
| set this, open your email account, pick "More Options", then the
| "Advanced" tab.
|
| We have documented this bug with Outlook 2007, 2003 and Express (with
| various patch levels, up to the most recent), running primarily on
| XP. The version of email server doesn't make any difference, e.g.
| Exchange, Unix, ISP, etc.
|
| I hope this is helpful.
|
| Mark Hays
|
|
|
|| For soem reason Outllok today started sending, somewhat arbitrarily,
|| multiple copies of certain email. it does not appear to be tied to
|| whether the email is addressed locally or not, nor does it seem to
|| replate to attachments. I have note encountered this problem with
|| Outlook before today (wed, 12/12/070, but I am wondering if
|| yesterday's patches are the culprit. Anyone else having this problem?