Windows Server

Guest

on Friday, user scheduled email in Outlook to delay send until Saturday
afternoon.

equipment failure caused exchange 2003 on SBS server to lose internet
access from Saturday morning until Sunday morning.

Local network connection was not broken, ie: Outlook clients stayed
connected to Exchange server during downtime. During downtime,
Exchange was sending thousands of delivery status notification 'delay'
messages to Outlook client regarding previously scheduled email that it
is now trying to send.

Upon reconnection of internet access, thousands of copies of the
scheduled email were sent out. User who scheduled the delayed email
received 4667 delivery status notifications.

Recipient received 9334 (double the number of delivery status
notifications) in his inbox. Needless to say, the recipient was not
having a good Monday. ;)

WTF?? Has anyone heard of this? Very confusing, wouldn't expect
Exchange to be set to freak out as it's default action when trying to
send a delayed email and not having a connection out.

Haven't found anything in searches to explain, hoping someone out there
has an idea.

Crina Li · Guest

Hi Darrenk,

Thank you for posting in SBS newsgroup.

We are performing further research on the issue. We will reply you as soon
as possible. Thanks for your understanding!

Best regards,

Crina Li (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.

=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: 1cixkom02@sneakemail.com
| Newsgroups: microsoft.public.windows.server.sbs
| Subject: delayed delivery options and offline server = mass email send
| Date: 7 Nov 2005 16:58:00 -0800
| Organization: http://groups.google.com
| |
| on Friday, user scheduled email in Outlook to delay send until Saturday
| afternoon.
|
| equipment failure caused exchange 2003 on SBS server to lose internet
| access from Saturday morning until Sunday morning.
|
| Local network connection was not broken, ie: Outlook clients stayed
| connected to Exchange server during downtime. During downtime,
| Exchange was sending thousands of delivery status notification 'delay'
| messages to Outlook client regarding previously scheduled email that it
| is now trying to send.
|
| Upon reconnection of internet access, thousands of copies of the
| scheduled email were sent out. User who scheduled the delayed email
| received 4667 delivery status notifications.
|
| Recipient received 9334 (double the number of delivery status
| notifications) in his inbox. Needless to say, the recipient was not
| having a good Monday. ;)
|
| WTF?? Has anyone heard of this? Very confusing, wouldn't expect
| Exchange to be set to freak out as it's default action when trying to
| send a delayed email and not having a connection out.
|
| Haven't found anything in searches to explain, hoping someone out there
| has an idea.
|
|

Crina Li · Guest

Hi,

I am sorry for the delayed response. We have done many researches on the
issue, however, due to the lack of the information, we can not find the
root cause of the issue. It may be caused by firewall between the Servers,
or any third party application. To narrow down the problem, would you
please help me confirm if you have enabled SMTP logging as following when
the situation occur?

1. Open the properties page of the Default SMTP Vitual Server in Exchange
System Manager.
2. On the General tab, check the "Enable logging" box.
3. Click Properties, click the Advanced tab and check all the boxes on the
list.
4. Click OK twice.
5. Stop and restart the SMTP virtual server.
6. Try reproducing the issue.
7. Stop the SMTP virtual server.
8. Go to the C:\WINDOWS\system32\LogFiles\SMTPSVC1 folder.

If you have enabled the log when the situation occurs, you can send me the
log for analysis and we will try to find if there is any useful information
to help us to find the root cause.

If you have not enabled the log when the situation occurs, due to the
complexity of this issue, the most efficient method to find the root cause
should be contact CSS for better support.

A suggestion would be to contact Microsoft Product Support Services via
telephone so that a dedicated Support Professional can assist with your
request. Please be advised that contacting phone support will be a charged
call. However, if you are simply requesting a hotfix be sent to you and no
other support then charges are usually refunded or waived.

To obtain the phone numbers for specific technology request please take a
look at the web site listed below.

http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.

Thanks for your understanding and I look forward to hearing from you.

Best regards,

Crina Li (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.

=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: 1cixkom02@sneakemail.com
| Newsgroups: microsoft.public.windows.server.sbs
| Subject: delayed delivery options and offline server = mass email send
| Date: 7 Nov 2005 16:58:00 -0800
| Organization: http://groups.google.com
| |
| on Friday, user scheduled email in Outlook to delay send until Saturday
| afternoon.
|
| equipment failure caused exchange 2003 on SBS server to lose internet
| access from Saturday morning until Sunday morning.
|
| Local network connection was not broken, ie: Outlook clients stayed
| connected to Exchange server during downtime. During downtime,
| Exchange was sending thousands of delivery status notification 'delay'
| messages to Outlook client regarding previously scheduled email that it
| is now trying to send.
|
| Upon reconnection of internet access, thousands of copies of the
| scheduled email were sent out. User who scheduled the delayed email
| received 4667 delivery status notifications.
|
| Recipient received 9334 (double the number of delivery status
| notifications) in his inbox. Needless to say, the recipient was not
| having a good Monday. ;)
|
| WTF?? Has anyone heard of this? Very confusing, wouldn't expect
| Exchange to be set to freak out as it's default action when trying to
| send a delayed email and not having a connection out.
|
| Haven't found anything in searches to explain, hoping someone out there
| has an idea.
|
|

delayed delivery options and offline server = mass email sen

	Windows Server Forum Index -> Small Business Server 2003	All times are GMT
Page 1 of 1