• Resolved Agnes

    (@agneslesagegmailcom)


    I have just sent my very first newsletter and something went very wrong…!

    The problem:
    I have 180 recipients, I selected all, and the newsletter has been sent to 380 recipients, but only 3 distinct emails received it in several dozens / hundred exemplaries.
    Thanks God, it is me, and 2 other administrators (and not someone else!).

    What may be specific in my setup…?
    – I disabled wp-cron and use a CPanel Cron from Hostgator that sends every 15 minutes.
    – I have set my Alo easymail settings to
    1> Maximum number of emails that can be sent in a 24-hr period: 10000
    2> Maximum number of emails that can be sent per batch: 100
    3> Interval between emails in a single batch, in milliseconds: 500
    – I use BWP minify to minify scripts, , I have set a number of scripts from alo easymail (but not exactly all) in its exceptions. See http://wordpress.org/support/topic/plugin-alo-easymail-newsletter-cant-send-after-update

    Else:
    – Everything semt to go fine, it shows 180 recipient and sending 100% completed.
    – I use a number of other plugins but I dont see a possible connection.
    – I have used some custom ooks for including multiple posts, but nothing else.
    – I use latest version of WP (3.4.2) and the plugin ()
    – I am hosted at Hostgator

    Since I can’t exactly try & test this million times, I’d be glad to have some insights!

    Agnes

    http://wordpress.org/extend/plugins/alo-easymail/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter Agnes

    (@agneslesagegmailcom)

    I have tried a new sendout with possibly problematicc plugins desativated: WP-cron contol (so normal WP-cron works), BWP minify (for the scripts) and BWP security.

    The strange things are:
    – it starts building list for 180 recipients
    – then seems to go to 200 and something
    Then when the ‘building recipient list’ is finished:
    – goes onto ‘on sending queue (0%)’ (I think first time it had not)
    Now I had to pause it before it continues, before the report shows ‘real’ users are beeing queued to receive several times.
    – Its now shows ‘total recipients: 98’
    – and if I look at the report, each recipient sems to be targeted between 1 and 4 times…

    I don’t get it!

    Somethign wrong with my settings?

    Plugin Author eventualo

    (@eventualo)

    Hi Agnes,
    multiple newsletters to same recipient could be related to too high values in settings.
    About yours:

    1> Maximum number of emails that can be sent in a 24-hr period: 10000
    2> Maximum number of emails that can be sent per batch: 100
    3> Interval between emails in a single batch, in milliseconds: 500

    the 2nd and/or 3rd are maybe too high. Each batch sending should take 100 x 0,500 = 50 seconds to complete and it could be a long time for a script and it could stop for reaching WP/php/server timeouts.
    And when there is stops or wrong behaviours, there could be multiple sendings.
    So the suggestion is to setup:
    2> Maximum number of emails that can be sent per batch: max 30
    3> Interval between emails in a single batch, in milliseconds: 0 (if you need 500 for your server policy, you have to reduce the emails per batch, above, eg. 10).
    You can set up debug newsletters (Newsletters > Settings > tab Newsletter) and make your sending tests. Let us know if these tips help you. (Sorry for my bad English).

    Thread Starter Agnes

    (@agneslesagegmailcom)

    Hi Alessandro
    I have set:
    1> Maximum number of emails that can be sent in a 24-hr period: 10000
    2> Maximum number of emails that can be sent per batch: 10
    3> Interval between emails in a single batch, in milliseconds: 500
    And newsletter debug: to log.
    I can see the queue of planned emails by checking the ‘report’ list.
    Unfortunately, I see a number of recipients appear stilol 2 times (up to 4). I see it in the report, as well as in the DB recipients table.
    What else may I do?

    It is a pity the system does not block/forbid creating multiple recipients from a single email address…

    Thread Starter Agnes

    (@agneslesagegmailcom)

    NB: the problem is not in sending… even prior to sending, the creation of the list is wrong, creating duplicates….
    So I wonder if those settings really matter?

    Thread Starter Agnes

    (@agneslesagegmailcom)

    OK, I have made multiple tests (thanks the great debugging function) and found out neither BWP-minify, nor Hypercache, nor my cron job, nor probably my Alo easymails settings were in fault, but there is an incompatibility with ‘DB cache reloaded fix’ plugin, that messes up the way Alo easymail creates the list of recipients.
    Disabling DB cache reloaded does fix the problem and creates a clean list without duplicates.

    My final setup thus is:
    – a 5mn cron job scheduled on my host Hostgator) though Cpanel, and WP-cron control plugin to control it
    – BWP minify with some exceptions for Alo easymail scripts (see other thread)
    – Hypercache on
    – DB cache relaoded fix DISABLED
    – Aloeasymail settings on:
    1> Maximum number of emails that can be sent in a 24-hr period: 10000
    2> Maximum number of emails that can be sent per batch: 10
    (I”d like to increase that though!)
    3> Interval between emails in a single batch, in milliseconds: 500
    That was suggested by my host.

    Thread Starter Agnes

    (@agneslesagegmailcom)

    PS: I realize the problem being with the building of recipient list, I also could use alternative methods as proposed in newsletter settings to build the recipient list.
    Yet I did not succeed:
    – ‘no ajax’ creates the list indeed, but seems to take forever to send and does not work with debugging mode..?
    – ‘ajax periodicupdater’ takes forever to create the list
    – ‘ajax loading only js….’ with DB cache reloaded plugin still creates multiple recipients.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘[Plugin: ALO EasyMail Newsletter] Serious Problem: 3 recipients received hundered emails…’ is closed to new replies.