[SOLVED] How to send emails before expiration day

Hello,

Is there a way or a plugin that could let us to send emails to the subscribers some speccific time before and after their expioration date?

Regards

CBSubs Mailer can do this. Please see your CBSubs documentation for CBSubs Mailer usage information. You can have it send emails any time before/after expiration, subscription date, etc.. Using CRON to trigger the emails once configured it'd be completely hands off and require no manual actions.

Thanks for the advise.

I created an mailer for sending one month before expiring some plan. But, it happened that the email was sent to every one which subscription will end one month later or before. There are even some that received it and their expiration date is one day from now.

In the parameter that says: "But do not send message if it's later than:" I put 1 week later. Thinking on scenarios like those.

Did I do something wrong? Or why did all those subscribers received it?


Another question: i click on the URL to process and send the mailers manually (not yet programmed in the cron), and I received a page that shows this message: "Processed 0 messages into the email queue. Sent 4 messages successfully."

But, in the sent messages window it shows 104 messages from that processing. Do you know how it could be that?

Regards

I suggest the below settings.

Automatically send message at following date: 1 month before
Relative to this date of the plans below: Subscription's Expiry Date
But do not send message if it's later than: 1 week after

With the above they should receive an email within 1 month of their subscription expiring. Please keep in mind if you just enabled this and you have users that are about to expire say in 2 days that is still within the 1 month before expiry window; so that's behaving normally.

Another question: i click on the URL to process and send the mailers manually (not yet programmed in the cron), and I received a page that shows this message: "Processed 0 messages into the email queue. Sent 4 messages successfully."

It means no new emails were added to the queue and 4 emails that were in the queue were sent.

But, in the sent messages window it shows 104 messages from that processing. Do you know how it could be that?

Believe that's the total emails sent by that mailer. It doesn't relate to a particular queue.

Thank you krileon. I suppose the best thing to send the first mailer was in the two stpe process. One for processing, and the other for sending. But maybe the second step could be manually filtered before sending them, so people with, say, 1 week from expiring, won't receive it. Isn't it?

Another question: i click on the URL to process and send the mailers manually (not yet programmed in the cron), and I received a page that shows this message: "Processed 0 messages into the email queue. Sent 4 messages successfully."

It means no new emails were added to the queue and 4 emails that were in the queue were sent.

But, in the sent messages window it shows 104 messages from that processing. Do you know how it could be that?

Believe that's the total emails sent by that mailer. It doesn't relate to a particular queue.[/quote]

The thing here is that it was the first mailer sent, so in this case the mails in the list of sent mails, waas supposed to be the same reported by the process. But, as I told, the process reported 4, and the list showed 104. And, I review the 104, and they surely were sent at the same time, in the same process.

Anyway, I will make more testing and report any special behavior.

Thank you krileon. I suppose the best thing to send the first mailer was in the two stpe process. One for processing, and the other for sending. But maybe the second step could be manually filtered before sending them, so people with, say, 1 week from expiring, won't receive it. Isn't it?

Well you could set the following and it'll do that automatically.

But do not send message if it's later than: 1 week before

This way it won't send emails if the user is within 1 week of expiring.

The alternative is to process the mailer so the queue is populated. Next delete whatever emails you don't want to send in the queue. Then process the queue.

The thing here is that it was the first mailer sent, so in this case the mails in the list of sent mails, waas supposed to be the same reported by the process. But, as I told, the process reported 4, and the list showed 104. And, I review the 104, and they surely were sent at the same time, in the same process.

Could be a counting bug. Please let me know if you see any other weird math issues like that when sending mailers.