throttling delay clarification
Question asked by Ben Conner - October 23, 2014 at 7:38 PM
Unanswered
Hi,
 
I have outbound throttling set to 100 messages/hour with the action of 'delay' if that is exceeded.
 
One user who periodically sends out blasts of several hundred from a billing application is reporting they are getting 421 messages during a billing cycle.
 
I interpreted the 'delay' action as accepting the email but not delivering more than 100/hour.  Is this not the correct interpretation?
 
Current release.
 
Thanks!
 
--Ben

4 Replies

Reply to Thread
0
Joe Wolf Replied
It sounds like your customer is getting the "message delayed" notice from SmarterMail if your throttling settings result in more attempts than you have set for sending out the message delayed notice. Depending on your spool retry settings the messages may or may not be delivered.

I think you should consider increasing the outgoing message limits for that user to avoid this problem.

-Joe
Thanks,
-Joe
0
Ben Conner Replied
Hi,

I 'fixed' the problem in the veterinarian sense by removing throttle limits for that domain for the moment. But the original question was in how to interpret the throttle delay choice in SM. The client's mail client was reporting 421 responses. I don't see them in the SMTP log file (at the detail level).

So does the 'throttle delay' option accept the emails and queue them, or reject the email from the client? I would assume since there is also a 'reject' option, it should do the former.

--Ben
0
Joe Wolf Replied
Throttle "Delay" just holds them in spool until the throttle criteria are lifted.

I have never experienced the situation you described, but the only scenario I know of that could cause the user to receive a message delayed notification on a throttled messed would be similar to the following scenario (and I'm not sure if this is the actual action of SmarterMail or not):

Let's say you have the domain throttled at 25 messages per hour, and you have the delayed message notification to be sent out after 4 attempts. The user attempts to send 200 messages. It would take a total of 8 non-throttled attempts to send out the messages.... so the sender might receive delayed message notifications for those throttled messages that take more than 4 attempts to send.

That's just my guess... once again I have never actually seen that scenario exist.

-Joe
Thanks,
-Joe
0
Ben Conner Replied
Actually removing the throttling on the domain didn't solve it. They got it again with no limits set. I'm clueless. It also isn't showing up in the log file.

I'm just going to tell them I have no way to track this down as there isn't a trace of the issue getting recorded anywhere.

--Ben

Reply to Thread