PowerMTA Support Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

PowerMTA 5.5r1 is out!!!!  Please contact support@port25.com for a license and download access.

Author Topic: Throttling based on Job-ID  (Read 59695 times)

slthomason

  • Jr. Member
  • **
  • Karma: +6/-17
  • Posts: 38
Throttling based on Job-ID
« on: September 14, 2012, 12:55:29 PM »

Hi there,

As we send a campaign, I was wondering if, as it was sending, if there was a way to throttle it based off the Job-ID.  Would there be a way to do that?  Does it have to be throttled at the beginning?  Can you throttle mid-sending of the campaign?

Thanks!
Logged

Port25-Admin2

  • Global Moderator
  • Hero Member
  • *****
  • Karma: +35/-1
  • Posts: 1527
Re: Throttling based on Job-ID
« Reply #1 on: September 14, 2012, 01:10:21 PM »

JobIDs are for tracking only.  You will need to use virtualMTAs if you want both tracking and control.

Logged

slthomason

  • Jr. Member
  • **
  • Karma: +6/-17
  • Posts: 38
Re: Throttling based on Job-ID
« Reply #2 on: September 14, 2012, 01:21:22 PM »

I am not sure if this is even possible, or even a good idea, but I will ask just for info's sake ...

Is it possible to dynamically create virtualMTAs on the fly?  Would it be possible to have a pool of IPs that got assigned a virtualMTA as it got dynamically created?  i.e. a virtualMTA for each campaign?

Figured I would ask ....
Logged

Port25-Admin1

  • Administrator
  • Hero Member
  • *****
  • Karma: +49/-4
  • Posts: 2361
Re: Throttling based on Job-ID
« Reply #3 on: September 14, 2012, 04:20:08 PM »

VirtualMTAs cannot be created on the fly.  The will need to be added to the configuration file prior to selecting them.  You could, however, automate the process of vmta creation, perhaps putting them in an include file.
Logged
Port25-Admin1
------------------
Try the following commands:
Quote
pmta show topdomains --errors
pmta show topqueues --errors
pmta --help

When PowerMTA won't start use:
Quote
pmtad --debug
When all else fails-->support@port25.com

slthomason

  • Jr. Member
  • **
  • Karma: +6/-17
  • Posts: 38
Re: Throttling based on Job-ID
« Reply #4 on: September 14, 2012, 04:49:39 PM »

What is totally possible.  What is the syntax for putting them in an include file?
Logged

Port25-Admin1

  • Administrator
  • Hero Member
  • *****
  • Karma: +49/-4
  • Posts: 2361
Re: Throttling based on Job-ID
« Reply #5 on: September 14, 2012, 04:59:48 PM »

global directive:
#
include /location/of/file
#

You can add anything to it that you would put in the regular config.
Logged
Port25-Admin1
------------------
Try the following commands:
Quote
pmta show topdomains --errors
pmta show topqueues --errors
pmta --help

When PowerMTA won't start use:
Quote
pmtad --debug
When all else fails-->support@port25.com

slthomason

  • Jr. Member
  • **
  • Karma: +6/-17
  • Posts: 38
Re: Throttling based on Job-ID
« Reply #6 on: November 12, 2012, 02:08:45 PM »

Let's say we went this approach and wanted to dynamically create virtual MTAs by adding such include files and calling pmta reload.  On a high-end scale, if this were happening multiple times per minute, what would the impact be?  We can probably get into a batching type scenario where it only reloads once every minute or so ... but what will the repercussions of this be?

Thanks!
Logged

Port25-Admin1

  • Administrator
  • Hero Member
  • *****
  • Karma: +49/-4
  • Posts: 2361
Re: Throttling based on Job-ID
« Reply #7 on: November 12, 2012, 02:18:23 PM »

Not a good idea to reload PowerMTA multiple times per minute.  If you do, it should be serialized, and not run in parallel.  Testing will show what works best in your environment.
Logged
Port25-Admin1
------------------
Try the following commands:
Quote
pmta show topdomains --errors
pmta show topqueues --errors
pmta --help

When PowerMTA won't start use:
Quote
pmtad --debug
When all else fails-->support@port25.com