Mountain View 1600, CA 94043
+1 650-253-0000
name@example.com
Web
Site
Search
Register
Login
DNN Home
Services
-
DotNetNuke Support
-
CRM Systems
DNN
-
DotNetNuke Modules
-
Module Downloads
-
Module Upgrade Policy
DNN Support
-
Module Update News
-
Knowledge Base
-
License Management
-
Invoice History
Module Downloads
Blog
Store
Contact Us
-
About Us
Search
Home
1
2
3
4
5
Home
Support
Bulk Emailer
Outgoing Mail Going too slow!
Previous
Next
8/11/2010 2:05 AM
Will
Joined: 9/19/2009
Posts: 55
Outgoing Mail Going too slow!
(United States)
Hi,
The outgoing mail for our Bulk Mailer module is taking an inordinate amount of time to send out approximately 35,000 e-mails. It used to take rougly 18 hours to send out the newsletter, now it's taking nearly twice that amount of time or two days. Any clue or tweak to the module that could fix the problem?
Thanks,
Will
8/11/2010 2:08 AM
Will
Joined: 9/19/2009
Posts: 55
Re: Outgoing Mail Going too slow!
(United States)
I just checked the site logs or Event Viewer and it reports that Bulk Mailer has completely crapped out?
THREAD ID
: 16
TYPE
: iwebs.Modules.BulkEmailer.EmailSchedule
EXCEPTION
: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
RESCHEDULED FOR
: 8/10/2010 11:08:35 AM
SOURCE
: STARTED_FROM_TIMER
ACTIVE THREADS
: 0
FREE THREADS
: 1
READER TIMEOUTS
: 0
WRITER TIMEOUTS
: 0
IN PROGRESS
: 0
IN QUEUE
: 9
Server Name
: GENERIC8
8/11/2010 2:11 AM
Will
Joined: 9/19/2009
Posts: 55
Re: Outgoing Mail Going too slow!
(United States)
I think this is related to the problem as well:
AssemblyVersion
: -1
PortalID
: -1
PortalName
:
UserID
: -1
UserName
:
ActiveTabID
: -1
ActiveTabName
:
RawURL
:
AbsoluteURL
:
AbsoluteURLReferrer
:
UserAgent
:
DefaultDataProvider
:
ExceptionGUID
:
InnerException
: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
FileName
:
FileLineNumber
: -1
FileColumnNumber
: -1
Method
:
StackTrace
:
Message
: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlDataReader.ConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(SqlConnection connection, SqlTransaction transaction, CommandType commandType, String commandText, SqlParameter[] commandParameters, SqlConnectionOwnership connectionOwnership) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) at iwebs.Modules.BulkEmailer.SqlDataProvider.GetJobDetailsFailed(Int32 JobItemId, DateTime InUse, DateTime InUseMinus30, Int32 LastFailed) at iwebs.Modules.BulkEmailer.JobDetailController.GetJobDetailsFailed(Int32 JobItemId, DateTime InUse, DateTime InUseMinus30, Int32 LastFailed) at iwebs.Modules.BulkEmailer.JobController.ProcessFailedJobs(JobInfo& objJob) at iwebs.Modules.BulkEmailer.JobController.DoEmailWork(String strLogFile) at iwebs.Modules.BulkEmailer.EmailSchedule.DoWork()
Source
:
Server Name
: GENERIC80
8/11/2010 2:17 AM
Will
Joined: 9/19/2009
Posts: 55
Re: Outgoing Mail Going too slow!
(United States)
Okay, I stopped and started the application pool and it crapped out again. Something is seriously wrong with the module.
Will
8/11/2010 3:09 AM
DNN Module Support
Joined: 8/28/2006
Posts: 2065
Re: Outgoing Mail Going too slow!
(Australia)
First up, did you read the section in the manual about increasing the performance of the module from default?
Ensure that you have not got anything dumb like 1 second set for the module job in the host scheduler.
If you would like us to take a look at your settings, then please contact us using our contact us page and make reference to this post URL.
8/11/2010 3:25 AM
Will
Joined: 9/19/2009
Posts: 55
Re: Outgoing Mail Going too slow!
(United States)
Yes, I read it over a year ago and set it to two minutes and try again in 10 minutes. What do you recommend for 35,000 users. You never gave any recommendations in the manual--other than 5 seconds. :-)
8/11/2010 3:32 AM
DNN Module Support
Joined: 8/28/2006
Posts: 2065
Re: Outgoing Mail Going too slow!
(Australia)
Page 81 of the current manual (not one a year old) has details about the send, and the fact that it sends 50 every round. i.e 50 every 2 min. So that should take about 23 hours to send 35 k.
If you set it to 1 min. or 40 seconds etc. you will see a speed increase. Additionally your server needs to be up to the job. Both the SMTP mail server, and the web server. We suggest that you set it as long as is reasonable, do get a good compromise between server load and, traffic data load, and keeping site performance.
Remember, that if you sen a big email, like .5 meg or something with a big attachment. The total send data volume can be huge. Your server needs to be able to be capable of sending this much data in the allocated time. Usually not a problem, but on some cheap hosting deals they throttle your max outbound data.
8/12/2010 1:37 AM
DNN Module Support
Joined: 8/28/2006
Posts: 2065
Re: Outgoing Mail Going too slow!
(Australia)
As it turns out, the user advised that their host was putting a limit of 200 messages per day on their outbound SMTP server. This naturally was the cause of their problem.
8/12/2010 1:40 AM
Will
Joined: 9/19/2009
Posts: 55
Re: Outgoing Mail Going too slow!
(United States)
Actually it turned out to be a limit of 200 messages per batch, not per day. Spoke with a junior engineer who didn't know what he was talking about. That said, could that still cause a problem?
Will
8/12/2010 2:17 AM
DNN Module Support
Joined: 8/28/2006
Posts: 2065
Re: Outgoing Mail Going too slow!
(Australia)
Well, technically we are only sending 50 a time. But they may need a pause between the start and finish of each job. If that is the case, it would probably run if you put a 5 min run time. but then it would take some time to execute a large number.
You can see the power of the module to allow you to get around these limits of host. It is easier to do when you understand their actual limits.
Remember too that we allow multiple SMTP server and limits on each to be configured.
8/12/2010 2:28 AM
Will
Joined: 9/19/2009
Posts: 55
Re: Outgoing Mail Going too slow!
(United States)
Ok, thanks David. This is indeed a good conversation for your customers to see. I have to "fess up" now and let you know that my site is on a shared non-dedicated server.My hosting outfit explained to me that I was essentially hogging the SMTP server each week from others on the shared server, with my mailings. That said, they recommended that I move to a virtual server arrangement, where I can send unlimited emails or newsletters and will not have an effect on others. This is what I was told orginally with the non-dedicated shared server, but apparently they must have receive complaints about me hogging resources, so decided to meter it. :-) Anyway, at 5 minutes, it would probably take 3 days to get out, so that's out of the question.
So, I will most likely move to a dedicated virtual hosting in short order and continue to use your module.
Will
11/24/2010 7:53 AM
Joined: 1/1/0001
Posts: 0
Re: Outgoing Mail Going too slow!
(United States)
Hello, we're experiencing similar lag in sending emails to a list of about 8000. Just recently it has started taking several days instead of one. The scheduler is set to every 2 minutes and retry in 10 - which hasn't changed. We're on a virtual dedicated mail server and do not have any daily cap that we're aware of. We also have dedicated web and sql servers that are performing normally.
The last email campaign had to be stopped at 74% after 4 days of running. Searching thru some email addresses, 4 from one company were sent and 2 had not been sent yet. So I'm curious if the bottleneck could be our mail server host throttling the ones that are sent (and if this can affect the ones in the queue), or if it sounds like something's amiss w/ the module itself. Our email list is continually growing, but probably only by a few hundred a month. Any troubleshooting tips would be appreciated. Thanks!
12/3/2010 3:46 AM
Joined: 1/1/0001
Posts: 0
Re: Outgoing Mail Going too slow!
(United States)
Not sure what exactly got this to work but the combination of some scheduler/dnn settings and our asking our mail server host for help resolved the issue. Thanks.
1/3/2011 3:22 AM
DNN Module Support
Joined: 8/28/2006
Posts: 2065
Re: Outgoing Mail Going too slow!
(Australia)
Almost certainly a limitation on the SMTP server send limit.
Page 1 of 1
Previous
Next
Home
Support
Bulk Emailer
Outgoing Mail Going too slow!