Microsoft IIS SMTP Service on Server 2008

I am using Microsoft's IIS SMTP service to relay email from within my network.  Essentially, emails of between 100K and 10MB are sent to one of two Server 2008 machines on the local subnet, and then forwarded to one of several email servers outside our subnet.  The emails originate from internal devices such as scanners.  All emails are sent with TLS enabled, and a check of the header shows that the emails are secured and there appear to be no unexpected intervening stops.

The problem is that sending the emails is extremely slow.  The SMTP service sends only one email at a time, and it is send very slowly.  This results in potentially long delays.  I can see no settings that will speed up the SMTP service.

It is possible that the email receiver is causing the delays.  I would like to:

1. Have the SMTP service send multiple emailssimultaneously, or
2. If someone could suggest an easy-to-maintain, low overhead SMTP server to install.  I have tried a few, but configuration can be quite complex as the SMTP servers I ahve looked at are designed to receive emails, something I don't need to do.

Thank you,

Harold Krongelb
Harold KrongelbPresident/Engineering SupervisorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

KimputerCommented:
In this case, even though it was made to store email, I'd use hMailServer (it's free!)
Very simple to use and understand.
You can have SMTP routes, and you can add rules to it. I think it suits your needs perfectly.
1
Dan McFaddenSystems EngineerCommented:
I've pumped more than 15K emails per hour thru IIS SMTP on Server 2008.  I am also currently using hMailServer for personal use and think that for a simple SMTP relay, IIS SMTP is easier to setup.

Can you post some of the following:

1. the SMTP server config
2. full SMTP header of a slow message
3. SMTP logs from IIS during the time when a slow message was sent
4. how much RAM the IIS SMTP server has
5. how much free disk space the IIS Server has
6. what network connectivity (speed) does the server have

How have you determined that the service is sending slowly?  Can you track the message from the create email process thru to the verified delivery?  And all points in between?

Dan
1
Harold KrongelbPresident/Engineering SupervisorAuthor Commented:
To answer your last questions, it is delays in the sending of the message.  When I look at the Current Sessions, I see messages take as many as 400 seconds to send.  There has also never been more than one message in the Current Sessions.  Note that all messages go to one of two destinations:  gmail.com or heimer.com.  Both destinations seem to exhibit the same issue, and I have never observed more than one session even when I know that there are emails to both destinations.

All Emails originate from 192.168.0.3, and the SMTP server is installed on the same machine (192.168.0.3).

1. The SMTP Server config is essentially the default, except that TLS transport is enabled on outbound security.

2. I believe this is a slow message:

Delivered-To: voicemail@home-inspection-ny.com
Received: by 10.114.28.195 with SMTP id d3csp345354ldh; Tue, 4 Aug 2015
 07:02:54 -0700 (PDT)
X-Received: by 10.170.213.198 with SMTP id e189mr3571964ykf.105.1438696973657;
 Tue, 04 Aug 2015 07:02:53 -0700 (PDT)
Return-Path: <Messenger@heimer.com>
Received: from Messenger.heimer.com (network-250.heimer.com. [75.127.164.250])
 by mx.google.com with ESMTPS id i200si1920590qhc.89.2015.08.04.07.02.51 for
 <voicemail@home-inspection-ny.com> (version=TLSv1.2
 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 04 Aug 2015 07:02:53 -0700
 (PDT)
Received-SPF: pass (google.com: domain of Messenger@heimer.com designates
 75.127.164.250 as permitted sender) client-ip=75.127.164.250;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of
 Messenger@heimer.com designates 75.127.164.250 as permitted sender)
 smtp.mail=Messenger@heimer.com
Received: from Messenger ([192.168.0.3]) by Messenger.heimer.com with
 Microsoft SMTPSVC(7.5.7601.17514); Tue, 4 Aug 2015 10:02:55 -0400
From: WIRELESS CALLER <Messenger@heimer.com>
To: <voicemail@home-inspection-ny.com>
Subject: Voicemail Message (WIRELESS CALLER > LVanHelden) From:6319210881
Date: Tue, 04 Aug 2015 10:02:55 -0400
X-Mailer: Voicemail Pro Server
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="{ee76f108-4dba-4b92-b71f-923f892bd79d}"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
Priority: Normal
Importance: Normal
Sensitivity: Normal
Content-Class: voice
X-CallingTelephoneNumber: 6319210881
X-VoiceMessageDuration: 94
X-VoiceMessageSenderName: WIRELESS CALLER
X-VoiceMessageOffset: 255
X-VoiceMessageReceivedTime: 3616149669
X-AttachmentOrder: ;MSG39217.WAV
X-MS-Has-Attach: yes
Return-Path: Messenger@heimer.com
Message-ID: <MESSENGERcobfpQOaVj00000ee9@Messenger.heimer.com>
X-OriginalArrivalTime: 04 Aug 2015 14:02:56.0024 (UTC)
 FILETIME=[43329180:01D0CEBE]

3.  Log file Attached

4. 8 GB RAM.  Task Manager says Commit is 3GB.

5.  120GB Free Disk Space

6.  The local network is all Gigabit.  The measured speeds on the internet connection are 74Mb down, and 37Mb up.

Also, CPU utilization are in the single digits, and Network utilization is less than 0.1%.

Thank you,

Harold
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Dan McFaddenSystems EngineerCommented:
So, according to the SMTP headers, this is the message track:

1. Message received by 10.170.213.198 at 04 Aug 2015 07:02:53 -0700 (PDT)... in UTC 14:02:53
2. Message is then received by mx.google.com from network-250.heimer.com at 04 Aug 2015 07:02:53 -0700 (PDT)... in UTC 14:02:53
3. Message is then received by 10.114.28.195 at 04 Aug 2015 07:02:54 -0700 (PDT)... in UTC 14:02:54
4. Message is then received by Messenger.heimer.com from Messenger ([192.168.0.3]) at 04 Aug 2015 10:02:55 -0400... in UTC 14:02:55

The message track look odd to me.  In 2 seconds, the message gets received by 10.170.213.198, relayed out to mx.google.com by network-250.heimer.com.  Then the message header then indicates that the email was received by 10.114.28.195 from no one and then received again by messenger.heimer.com from messenger [192.168.03]

Either way, this is not a slow message.  It was received by 4 different IPs in 2 seconds.

My questions are:
1. at what time did the device that generated the message, start sending?
2. how is the device or origin (scanner?) configured to connect to the network?
3. what devices are at:  10.114.28.195 & 10.170.213.198?
4. where is the log file, I don't see an attachment?

I'd assume the process looks like this:

1. device send an SMTP message to internal SMTP relay
2. internal SMTP server scans the message header for destination domain(s)
3. internal SMTP server resolves MX records for the destination domain(s)
4. internal SMTP server starts (E)SMTP conversation with a host designated by the destination domain MX records
5. internal SMTP server relays message to destination domain SMTP server

Dan
1
Harold KrongelbPresident/Engineering SupervisorAuthor Commented:
I am investigating whehter SMTP sender is slow.  There is a 10-minute to 3-hour delay in message delivery, which does not appear to be reflected in the logs.  Although the SMTP sender reports its emails sent immediately, the SMTP sender may be queuing the emails.  I will investigate this further.
0
KimputerCommented:
Very simple to check. Install Wireshark on the mail server (or SMTP relay). Then start capture on port 25, and in no time (or long waiting time if it's indeed a problem somewhere), you will see the traffic appear. First the acceptance from the scanner to this relay, then the outgoing email to the final destination.
0
Dan McFaddenSystems EngineerCommented:
The SMTP protocol has a built delivery retry process which compensates for a remote host not being immediately available. The log entries will indicate what may be going on during the delivery process.  If you post some SMTP logs, it may help speed up the tr

Is the delay across the board for all messages, or only a percentage of the emails?

Dan
1
Harold KrongelbPresident/Engineering SupervisorAuthor Commented:
It appears to affect all messages.  The logs are attached.  ex150804.log
0
Dan McFaddenSystems EngineerCommented:
The logs are useless.  You need to edit the log settings and turn on all fields.

1. Go into IIS 6 Manger
2. Right click the SMTP Virtual Server object
3. Select Properties
4. Enable Logging on the General Tab
5. Click the Properties button
6. Under the Logging Properties box, click the Advanced Tab
7. Enable all fields
8. OK your way out.

This way you will see a more detailed log entry for each step in the SMTP conversation.

Dan
0
Harold KrongelbPresident/Engineering SupervisorAuthor Commented:
Detailed log snippet.

#Software: Microsoft Internet Information Services 7.5
#Version: 1.0
#Date: 2015-08-06 13:26:56
#Fields: date time c-ip cs-username s-sitename s-computername s-ip s-port cs-method cs-uri-stem cs-uri-query sc-status sc-win32-status sc-bytes cs-bytes time-taken cs-version cs-host cs(User-Agent) cs(Cookie) cs(Referer)
2015-08-06 13:26:56 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 QUIT - Messenger 240 288820 105 4 288758 SMTP - - - -
2015-08-06 13:26:56 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 EHLO - +Messenger 250 0 197 14 0 SMTP - - - -
2015-08-06 13:26:56 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 MAIL - +FROM:<Messenger@heimer.com> 250 0 45 32 0 SMTP - - - -
2015-08-06 13:26:56 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 RCPT - +TO:<voicemail@home-inspection-ny.com> 250 0 45 42 0 SMTP - - - -
2015-08-06 13:31:39 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 QUIT - Messenger 240 282721 105 4 282705 SMTP - - - -
2015-08-06 13:31:39 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 EHLO - +Messenger 250 0 197 14 0 SMTP - - - -
2015-08-06 13:31:39 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 MAIL - +FROM:<Messenger@heimer.com> 250 0 45 32 0 SMTP - - - -
2015-08-06 13:31:39 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 RCPT - +TO:<voicemail@home-inspection-ny.com> 250 0 45 42 0 SMTP - - - -
2015-08-06 13:36:28 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 QUIT - Messenger 240 289117 105 4 289055 SMTP - - - -
2015-08-06 13:36:28 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 EHLO - +Messenger 250 0 197 14 0 SMTP - - - -
2015-08-06 13:36:28 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 MAIL - +FROM:<Messenger@heimer.com> 250 0 45 32 0 SMTP - - - -
2015-08-06 13:36:28 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 RCPT - +TO:<voicemail@home-inspection-ny.com> 250 0 45 42 0 SMTP - - - -
2015-08-06 13:41:13 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 QUIT - Messenger 240 284889 105 4 284811 SMTP - - - -
2015-08-06 13:41:13 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 EHLO - +Messenger 250 0 197 14 0 SMTP - - - -
2015-08-06 13:41:13 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 MAIL - +FROM:<Messenger@heimer.com> 250 0 45 32 0 SMTP - - - -
2015-08-06 13:41:13 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 RCPT - +TO:<voicemail@home-inspection-ny.com> 250 0 45 42 0 SMTP - - - -
2015-08-06 13:45:57 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 QUIT - Messenger 240 283017 105 4 282970 SMTP - - - -
2015-08-06 13:45:57 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 EHLO - +Messenger 250 0 197 14 0 SMTP - - - -
2015-08-06 13:45:57 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 MAIL - +FROM:<Messenger@heimer.com> 250 0 45 32 0 SMTP - - - -
2015-08-06 13:45:57 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 RCPT - +TO:<MessageCenter@heimer.com> 250 0 37 34 0 SMTP - - - -
2015-08-06 13:50:52 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 QUIT - Messenger 240 295091 105 4 295060 SMTP - - - -
2015-08-06 13:50:53 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 EHLO - +Messenger 250 0 197 14 0 SMTP - - - -
2015-08-06 13:50:53 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 MAIL - +FROM:<Messenger@heimer.com> 250 0 45 32 0 SMTP - - - -
2015-08-06 13:50:53 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 RCPT - +TO:<voicemail@home-inspection-ny.com> 250 0 45 42 0 SMTP - - - -
2015-08-06 13:51:53 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 DATA - <MESSENGERXRPmcarcR400001105@Messenger.heimer.com> 250 0 133 5236922 59062 SMTP - - - -
2015-08-06 13:51:53 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 QUIT - Messenger 240 59124 69 4 0 SMTP - - - -
2015-08-06 13:51:53 74.125.29.27 OutboundConnectionResponse SMTPSVC1 MESSENGER - 0 - - 220+mx.google.com+ESMTP+l88si11845545qge.125+-+gsmtp 0 0 52 0 187 SMTP - - - -
2015-08-06 13:51:53 74.125.29.27 OutboundConnectionCommand SMTPSVC1 MESSENGER - 0 EHLO - Messenger.heimer.com 0 0 4 0 187 SMTP - - - -
2015-08-06 13:51:53 74.125.29.27 OutboundConnectionResponse SMTPSVC1 MESSENGER - 0 - - 250-mx.google.com+at+your+service,+[75.127.164.250] 0 0 51 0 219 SMTP - - - -
2015-08-06 13:51:53 74.125.29.27 OutboundConnectionCommand SMTPSVC1 MESSENGER - 0 STARTTLS - - 0 0 8 0 219 SMTP - - - -
2015-08-06 13:51:53 74.125.29.27 OutboundConnectionResponse SMTPSVC1 MESSENGER - 0 - - 220+2.0.0+Ready+to+start+TLS 0 0 28 0 234 SMTP - - - -
2015-08-06 13:51:53 74.125.29.27 OutboundConnectionCommand SMTPSVC1 MESSENGER - 0 EHLO - Messenger.heimer.com 0 0 4 0 312 SMTP - - - -
2015-08-06 13:51:53 74.125.29.27 OutboundConnectionResponse SMTPSVC1 MESSENGER - 0 - - 250-mx.google.com+at+your+service,+[75.127.164.250] 0 0 51 0 328 SMTP - - - -
2015-08-06 13:51:53 74.125.29.27 OutboundConnectionCommand SMTPSVC1 MESSENGER - 0 MAIL - FROM:<Messenger@heimer.com>+SIZE=5237242 0 0 4 0 328 SMTP - - - -
2015-08-06 13:51:53 74.125.29.27 OutboundConnectionResponse SMTPSVC1 MESSENGER - 0 - - 250+2.1.0+OK+l88si11845545qge.125+-+gsmtp 0 0 41 0 359 SMTP - - - -
2015-08-06 13:51:53 74.125.29.27 OutboundConnectionCommand SMTPSVC1 MESSENGER - 0 RCPT - TO:<voicemail@home-inspection-ny.com> 0 0 4 0 359 SMTP - - - -
2015-08-06 13:51:54 74.125.29.27 OutboundConnectionResponse SMTPSVC1 MESSENGER - 0 - - 250+2.1.5+OK+l88si11845545qge.125+-+gsmtp 0 0 41 0 999 SMTP - - - -
2015-08-06 13:51:54 74.125.29.27 OutboundConnectionCommand SMTPSVC1 MESSENGER - 0 BDAT - 5237242+LAST 0 0 4 0 999 SMTP - - - -
2015-08-06 13:51:57 74.125.29.27 OutboundConnectionResponse SMTPSVC1 MESSENGER - 0 - - 250+2.0.0+OK+l88si11845545qge.125+-+gsmtp 0 0 41 0 3698 SMTP - - - -
2015-08-06 13:51:57 74.125.29.27 OutboundConnectionCommand SMTPSVC1 MESSENGER - 0 QUIT - - 0 0 4 0 3698 SMTP - - - -
2015-08-06 13:51:57 74.125.29.27 OutboundConnectionResponse SMTPSVC1 MESSENGER - 0 - - 221+2.0.0+closing+connection+l88si11845545qge.125+-+gsmtp 0 0 57 0 3729 SMTP - - - -
2015-08-06 13:52:02 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 EHLO - +Messenger 250 0 197 14 0 SMTP - - - -
2015-08-06 13:52:02 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 MAIL - +FROM:<Messenger@heimer.com> 250 0 45 32 0 SMTP - - - -
2015-08-06 13:52:02 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 RCPT - +TO:<LynetteV@heimer.com> 250 0 32 29 0 SMTP - - - -
2015-08-06 13:56:50 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 QUIT - Messenger 240 288383 105 4 288352 SMTP - - - -
2015-08-06 13:56:50 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 EHLO - +Messenger 250 0 197 14 0 SMTP - - - -
2015-08-06 13:56:50 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 MAIL - +FROM:<Messenger@heimer.com> 250 0 45 32 0 SMTP - - - -
2015-08-06 13:56:50 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 RCPT - +TO:<voicemail@home-inspection-ny.com> 250 0 45 42 0 SMTP - - - -
2015-08-06 14:01:37 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 QUIT - Messenger 240 285700 105 4 285653 SMTP - - - -
2015-08-06 14:01:37 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 EHLO - +Messenger 250 0 197 14 0 SMTP - - - -
2015-08-06 14:01:37 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 MAIL - +FROM:<Messenger@heimer.com> 250 0 45 32 0 SMTP - - - -
2015-08-06 14:01:37 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 RCPT - +TO:<voicemail@home-inspection-ny.com> 250 0 45 42 0 SMTP - - - -
2015-08-06 14:06:24 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 QUIT - Messenger 240 287353 105 4 287307 SMTP - - - -
2015-08-06 14:06:24 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 EHLO - +Messenger 250 0 197 14 0 SMTP - - - -
2015-08-06 14:06:24 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 MAIL - +FROM:<Messenger@heimer.com> 250 0 45 32 0 SMTP - - - -
2015-08-06 14:06:24 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 RCPT - +TO:<voicemail@home-inspection-ny.com> 250 0 45 42 0 SMTP - - - -
2015-08-06 14:11:11 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 QUIT - Messenger 240 286371 105 4 286325 SMTP - - - -
2015-08-06 14:11:11 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 EHLO - +Messenger 250 0 197 14 0 SMTP - - - -
2015-08-06 14:11:11 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 MAIL - +FROM:<Messenger@heimer.com> 250 0 45 32 0 SMTP - - - -
2015-08-06 14:11:11 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 RCPT - +TO:<voicemail@home-inspection-ny.com> 250 0 45 42 0 SMTP - - - -
2015-08-06 14:15:54 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 QUIT - Messenger 240 282440 105 4 282409 SMTP - - - -
2015-08-06 14:15:54 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 EHLO - +Messenger 250 0 197 14 0 SMTP - - - -
2015-08-06 14:15:54 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 MAIL - +FROM:<Messenger@heimer.com> 250 0 45 32 0 SMTP - - - -
2015-08-06 14:15:54 192.168.0.3 Messenger SMTPSVC1 MESSENGER 192.168.0.3 0 RCPT - +TO:<MessageCenter@heimer.com> 250 0 37 34 0 SMTP - - - -
0
KimputerCommented:
Still think a Wireshark log is more usefull. You will get to see exactly why it's rejected. This current log still misses some important information.
0
Dan McFaddenSystems EngineerCommented:
OK, in the log snippet, I see only 1 email of any size coming thru the SMTP relay.  The email was about 5MB+ and it took 59ms to pass off the message.

What I do see that looks weird to me, it that several messages are sent by a user named Messenger from 192.168.0.3 to itself at 192.168.0.3 and these transactions are taking between 280 and 300 seconds to quit.  It looks as if the client is not ending the SMTP conversation correctly and the SMTP session timeout may be kicking the session.

How are these devices sending the email?

The email with the 5MB+ payload, appears to have hit the relay at 13:51:53 and successfully delivered to Gmail at 13:51:57.  No delay.

My question is... what is this:

06.08.2015	13:36:28	192.168.0.3	Messenger	SMTPSVC1	MESSENGER	192.168.0.3	0	EHLO	-	#NAME?	250	0	197	14	0	SMTP	-	-	-	-
06.08.2015	13:36:28	192.168.0.3	Messenger	SMTPSVC1	MESSENGER	192.168.0.3	0	MAIL	-	+FROM:<Messenger@heimer.com>	250	0	45	32	0	SMTP	-	-	-	-
06.08.2015	13:36:28	192.168.0.3	Messenger	SMTPSVC1	MESSENGER	192.168.0.3	0	RCPT	-	+TO:<voicemail@home-inspection-ny.com>	250	0	45	42	0	SMTP	-	-	-	-
06.08.2015	13:41:13	192.168.0.3	Messenger	SMTPSVC1	MESSENGER	192.168.0.3	0	QUIT	-	Messenger	240	284889	105	4	284811	SMTP	-	-	-	-
06.08.2015	13:41:13	192.168.0.3	Messenger	SMTPSVC1	MESSENGER	192.168.0.3	0	EHLO	-	#NAME?	250	0	197	14	0	SMTP	-	-	-	-
06.08.2015	13:41:13	192.168.0.3	Messenger	SMTPSVC1	MESSENGER	192.168.0.3	0	MAIL	-	+FROM:<Messenger@heimer.com>	250	0	45	32	0	SMTP	-	-	-	-
06.08.2015	13:41:13	192.168.0.3	Messenger	SMTPSVC1	MESSENGER	192.168.0.3	0	RCPT	-	+TO:<voicemail@home-inspection-ny.com>	250	0	45	42	0	SMTP	-	-	-	-
06.08.2015	13:45:57	192.168.0.3	Messenger	SMTPSVC1	MESSENGER	192.168.0.3	0	QUIT	-	Messenger	240	283017	105	4	282970	SMTP	-	-	-	-

Open in new window


Notice the the 2 QUIT commands and the time-taken (in ms).  That's 284.8sec and 282.9sec to affect a QUIT.  Not normal.

Dan
1
Dan McFaddenSystems EngineerCommented:
@Kimputer:  You get exactly the reason for rejecting in the SMTP logs.  You will see a return code in the 400 or 500 range.

I agree sniffing traffic is useful but you get a flood of data and you need someone who can read the conversation.  Not always easy to do.

Scraping thru logs is much easier and much faster.  Especially when one spend a significant part of their day analyzing logs.

Dan
1
Harold KrongelbPresident/Engineering SupervisorAuthor Commented:
User Messenger is the sender, and the message is a WAV file.  Both the Sender and the SMTP service reside on the machine with the 192.168.0.3 IP address.

It appears that the transaction that never leaves the machine takes 200 to 300 seconds, while the transaction outside the machine is much quicker.

The delays come as a result of the WAV files coming in much faster than the SMTP service accepts them.  This causes the messages to back up, and I see 30+ minute delays.  It appears that the SMTP sender is at fault, so I need to go back to the SMTP sender's vendor.  Unfortunately, the SMTP sender created by Avaya, and Avaya condsiders all bugs related to SMTP to be caused by the fact that I am not running on their UNIX platform.
0
Dan McFaddenSystems EngineerCommented:
Then I would look into any updates or upgrades for this Avaya software.

Are you sure the configuration of the Avaya software is correct?

Also, if you're using it in an unsupported configuration and the configuration is causing pain points for you, then maybe you should consider migrating to supported system config or switching to a system that supports your OS platform.

Dan
1

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Harold KrongelbPresident/Engineering SupervisorAuthor Commented:
It turns out that the program connecting to the SMTP service was causing the problem.  Apparently, it was trying to deliver emails bigger than the sender's email program could handle (but well below the IIS SMTP limit).  The sender's email program went to its limit, and stopped.  This program than tried to resend this email.  What caused the slowdown was multiple emails too large for the sending email program.  The sender email program would only send one email at a time, and small legit emails had to wait behind the queue, which grew to be hours long.  The sending program failed to correctly log what it was doing.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft IIS Web Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.