1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

interspire question - interspire sending to only 500 email chunks at a time

Discussion in 'Black Hat SEO Tools' started by m73022, Feb 24, 2012.

  1. m73022

    m73022 Newbie

    Joined:
    Apr 25, 2008
    Messages:
    45
    Likes Received:
    39
    hey everyone, have a question that im sure someone can help me with in regards to interspire.

    IEM seems to only send email campaigns to the list in chunks of 500 each??

    i read that there is a function in the api.php and the job_send.php pages that shows a limit of 500 but have no idea how to fix this issue?

    my server and settings are all set to unlimited so its not a hosting or cron job issue, its the script and this built in function itself.

    wondering if anyone knows how to adjust this function so it sends all together in one mailing, not stop and pause after every 500 email chunks.

    i have tried just changing the 500 to a higher number but then the mailing just seems to sit and says "In Progress" but no progress is ever made. any help from someone that has had this issue or knows coding would be awesome.
     
  2. bhconsultant

    bhconsultant Junior Member

    Joined:
    May 24, 2010
    Messages:
    117
    Likes Received:
    12
    I too would be interested in finding out.
     
  3. kvmcable

    kvmcable Supreme Member

    Joined:
    Dec 28, 2010
    Messages:
    1,355
    Likes Received:
    2,815
    Occupation:
    24 year business owner - old school dude
    Location:
    KFC - BW3
    What version are you running? I've been running IEM for years and never had this problem. I send about 100,000 emails a week (4 times 25,000 list). I have my cron set up at 5 min intervals and then set up 5 min intervals under Settings tab.

    Try throttling your send rate or you'll surely get banned by major ISPs. Also split your lists between different IPs so if you hit a softblock on one account all your emails to that ISP won't fail. For my 25k list I send on 5 different IPs 5k lists each. That solves a lot of problems with delivery. Plus it speeds up my send rate. I send at 100 per hr per account so I don't get softblocked by majors. You hammer a major ISP with 500 an hr from 1 IP and you won't get much delivered. You'll then get slammed by your host when thousands of emails bounce and cause all sorts of other issues (poor reputation scores, etc).

    Throttle and split so your list lives longer, you'll get better delivery and keep shit from hitting the fan with your ISP. Most servers on a good day can send 3000-4000 an hr but delivery is a whole different issue. All the major ISPs will softblock you if you hit their servers too often an hour from 1 IP or some even from one server (host).

    Good luck.
     
    Last edited: Mar 9, 2012
  4. gsquared

    gsquared Newbie

    Joined:
    Jan 12, 2009
    Messages:
    11
    Likes Received:
    4
    KVMCable, isn't there a way to setup Interspire to rotate IPs? I read that in another thread here in BHW. I just installed IEM and I'm trying to figure out the best way to do this too.
     
  5. itzfritz

    itzfritz Newbie

    Joined:
    Apr 6, 2010
    Messages:
    40
    Likes Received:
    11
    What I believe is happening here is IEM is just dividing the delivery into chunks of 500 recipients in order to reduce the effect that the 'load recipient information' db-query overhead would have on the send process; there may be a ton of data that is required for a specific send job, especially if your subscriber records have custom fields, and/or if you're sending to a list segment instead of an entire list, and/or if your email creative has tracking links that need to be regenerated for each recipient etc.. If you had a campaign of 100K recipients, and IEM loaded/calculated all the required data for all recipients, from the db, into RAM, at one time, your send process would have to wait until that time-consuming process is complete ('blocking'), and it may/would additionally be affected by the resources that were consumed by that data.

    This 500-recipient chunk may not be right for your particular setup though- you may have lots of ram, or you may have a dedicated db server, and you may be able to support a larger batch of recipients. In this case, it's real easy to change, it;s just a 'for' loop somewhere in the code. It should really be a configurable variable, but hey if IEM was perfect there wouldnt be work for guys like me.

    It might look something like this:
    Code:
    until sending is complete:
      subscribers = load_subscribers(500) # long blocking operation
      for each subscriber in subscribers:
        send to subscriber
    
    Which is better than
    Code:
    
    HTH
     
  6. jdothat

    jdothat Newbie

    Joined:
    Jun 1, 2012
    Messages:
    1
    Likes Received:
    0
    m73022,

    I'm not sure if you're still experiencing problems but if you want to manually configure the number of emails placed in each chunk (Interspire 6.0+ does group the emails) you will need to modify the jobs_send.php file (found in the functions/api folder, line 330). To my knowledge it's the only file that controls that number.

    A few things to consider...
    1. Interspire will only send that "chunk" number for the entire hour so expect the next chunk of 500 (or whatever number you specify) to take place a hour later. Example: I have a list of 50K and I set the "chunk" variable to 5K. IEM will send that 5K as fast as it can but won't send again for another hour. That would essentially mean the total send time for that campaign will be 10 hours. If you want to send to the entire list just bump that number up 50K but be very mindful of the implications of doing so.

    2. What I don't know is how IEM determines how to only send the chunks every hour. I'm still searching for that and when I find it i'll let you know.

    3. As mentioned before (by kvmcable) I'd recommend sending in chunks and even consider splitting your list up by isp (hotmail, yahoo, aol) and pacing yourself regardless of the IP you're sending off of. You basically just want to know what's going on and be able to adjust or pause the emails in case there is a temporary block placed at the ISP level. No reason to stop sending the email entirely if you're having delivery problems at yahoo.

    Hope this helps.
    -J
     
  7. wasif

    wasif Newbie Premium Member

    Joined:
    Oct 8, 2009
    Messages:
    49
    Likes Received:
    31
    Occupation:
    Information Technology
    Location:
    Lahore, Pakistan
    Home Page:
    Interspire doesn't rotate IPs. You'll need to use smtp application which allows to rotate IPs. Like Power MTA or any other.

     
  8. m1xf1

    m1xf1 Registered Member

    Joined:
    Jan 1, 2012
    Messages:
    55
    Likes Received:
    7
    Check your hosting. This made a difference. Most hosts have a 500 per day limitation.
     
  9. p33kay

    p33kay Newbie

    Joined:
    Jul 18, 2011
    Messages:
    4
    Likes Received:
    2
    its a common database problem and ive had it on all my interspire servers.

    The application queries the database for batches of 500 recipients each time the scheduled sending job runs. So if your database is not responding quickly enough it could just sit there as you're experiencing.

    First you should try setting the application to query for a smaller number of recipients. You can do that by editing /admin/functions/api/jobs_send.php. Before you do this make sure you pause any running campaigns! In that file on line 339 you should find something like this:

    while ($recipients = $this->FetchFromQueue($queueid, 'send', 1, 500)) {


    On that line just change 500 to something smaller such as 200 and then resume


    Increase memory limits in php.ini file as well as mem limit in init.php file in interspire
     
  10. EliassDaamate

    EliassDaamate Newbie

    Joined:
    Jul 5, 2012
    Messages:
    21
    Likes Received:
    0
    yes its a good one
     
  11. alexbraila90

    alexbraila90 BANNED BANNED

    Joined:
    Jan 3, 2012
    Messages:
    63
    Likes Received:
    20
    Increase the memory_limit in your php.ini file and that will solve your problem.