• mailall.js

    From Access Denied@PHARCYDE to Digital Man on Sunday, May 23, 2010 08:28:41
    Hey DM,

    Back roughly a year ago you made me a bulk email mod called mailall.js (based off bulkmail.js, but with the ability of using javascript to send them account information, etc). I'm routing through my SMTP server via my ISP just fine, but it seems as though after it sends out some emails, it starts giving me errors of "421 Connection rate too high, try again later [R0203001]."

    Is there a way to slow this process down so that it doesn't connect so fast? Or is it just because of the _amount_ of connections? I believe it was trying to send out about 230 emails in under a minute, and after about 100 it started giving me that error message. Maybe if there was a delay in between messages going out it would fix this? I guess it doesn't matter how long it takes to get done, as long as it works for every email.

    axisd

    ---
    ■ Synchronet ■ thePharcyde_ >> telnet://bbs.pharcyde.org (Wisconsin)
  • From Digital Man to Access Denied on Monday, May 24, 2010 16:45:37
    Re: mailall.js
    By: Access Denied to Digital Man on Sun May 23 2010 08:28 am

    Hey DM,

    Back roughly a year ago you made me a bulk email mod called mailall.js (based off bulkmail.js, but with the ability of using javascript to send them account information, etc). I'm routing through my SMTP server via my ISP just fine, but it seems as though after it sends out some emails, it starts giving me errors of "421 Connection rate too high, try again later [R0203001]."

    Is there a way to slow this process down so that it doesn't connect so
    fast? Or is it just because of the _amount_ of connections? I believe it
    was trying to send out about 230 emails in under a minute, and after about 100 it started giving me that error message. Maybe if there was a delay in between messages going out it would fix this? I guess it doesn't matter how long it takes to get done, as long as it works for every email.

    What you want is to throttle the sendmail thread. This isn't really a JavaScript question, unless you want to queue up 100 e-mails at a time, wait for an hour or so, then another hundred. It'd probably easy to just add some kind of throttle support to the sendmail thread, which it currently doesn't have. I'll look into adding a configuration parameter.

    digital man

    Snapple "Real Fact" #127:
    A hummingbird's heart beats 1,400 times a minute.
  • From Tracker1@TRN to Access Denied on Monday, May 24, 2010 19:32:53
    Access Denied > Is there a way to slow this process down so that it doesn't connect so fast? Or
    is it just because of the _amount_ of connections? I believe it was trying to send out about 230 emails in under a minute, and after about 100 it started giving me that error message. Maybe if there was a delay in between messages going out it would fix this? I guess it doesn't matter how long it takes to get
    done, as long as it works for every email.

    You can slow it down going into SMTP, not sure if there's a setting in the smtp server to slow/delay delivery.

    Some ISPs will start doing the 4xx errors if more than 100 emails an hour or day go through, you may need to ask them about it.

    --
    Michael J. Ryan - http://tracker1.info/

    ---
    ■ Synchronet ■ Roughneck BBS - telnet://roughneckbbs.com - www.roughneckbbs.com
  • From Access Denied@PHARCYDE to Digital Man on Monday, May 24, 2010 20:55:01
    Re: mailall.js
    By: Digital Man to Access Denied on Sat Mar 08 2025 07:48 am

    What you want is to throttle the sendmail thread. This isn't really a JavaScript question, unless you want to queue up 100 e-mails at a time, wait for an hour or so, then another hundred. It'd probably easy to just add some kind of throttle support to the sendmail thread, which it currently doesn't have. I'll look into adding a configuration parameter.

    I didn't really know how my question would be answered, and since 8 ran into the problem while running mailall.js I figured I'd post about it here. Other than that, your idea sounds great and I can't wait to see it implemented! :)

    axisd

    ---
    ■ Synchronet ■ thePharcyde_ >> telnet://bbs.pharcyde.org (Wisconsin)
  • From Jas Hud@DARKSANC to Access Denied on Monday, August 16, 2010 15:49:35
    Re: mailall.js
    By: Digital Man to Access Denied on Sat Mar 08 2025 07:48 am

    What you want is to throttle the sendmail thread. This isn't really a JavaScript question, unless you want to queue up 100 e-mails at a time, wait for an hour or so, then another hundred. It'd probably easy to just add some kind of throttle support to the sendmail thread, which it currently doesn't have. I'll look into adding a configuration parameter.

    I didn't really know how my question would be answered, and since 8 ran
    into the problem while running mailall.js I figured I'd post about it here. Other than that, your idea sounds great and I can't wait to see it implemented! :)



    our isp will stop sending after around 20 emails, what you want to do is temporarily disable your forwarding through the email server and send it direct.
    this means that it will sometimes go in their spam folder [or be denied]depending on their mail service.

    throttling wont really help since RR will block you if you send out too many a day.... unless you crank it down to a ridiculous level.

    ---
    ■ Synchronet ■ Dark Sanctuary darksanctuary.servebbs.com
  • From Access Denied@PHARCYDE to Jas Hud on Monday, August 16, 2010 20:57:45
    Re: Re: mailall.js
    By: Jas Hud to Access Denied on Mon Aug 16 2010 03:49 pm

    our isp will stop sending after around 20 emails, what you want to do is temporarily disable your forwarding through the email server and send it direct.
    this means that it will sometimes go in their spam folder [or be denied]depending on their mail service.

    throttling wont really help since RR will block you if you send out too many day.... unless you crank it down to a ridiculous level.

    I figured it out soon after I posted that. I just added a delay in between every post. So that it didn't do so many so fast. And it seemed to work just fine. That was awhile ago though... In that time I've gone from over 300 users down to about 75, since I changed the inactivity deletion from one year to like 30 or 60 days. If they're not going to call for 2 months, they can reapply. :)

    axisd

    ---
    ■ Synchronet ■ thePharcyde_ >> telnet://bbs.pharcyde.org (Wisconsin)