I Just installed the newest version of Newsletter Studio 2 to my Umbraco 7 install. Our company developed a newsletter package before, but maintaining it was very time consuming. We decided to test Newsletter Studio, I've been very supprised with the clean UI en features.
But, the bounce feature is not working as aspected. I added some subscribers with a faulty email addresses. I added a account for receiving bouncers at our mailserver. And I but the settings in de config of Newsletter Studio. It works al fine up to the moment it has to collect these bounce mails, I see them in de mailbox, and set the subscriber to "Bounced".
Bounce mail looks like this: Could not deliver message to the following recipient(s):
Let me see if I understand your problem correct. So this is the case:
The emails are sent to "falty" emails and these servers respond with an error to your bounce-mailbox (1. Did you confirm this with an email client?). Then newsletter studio looks at the mailbox and process the bouncemails and sets the current subscriber to unsubscribed status "Bounced"? (2. Does this work?).
That's the expected behavior - what is the "problem" in this process?
=D
Does it send to them again after they have been set as Bounced?
Glad to read your response, but i see i forget to write the word NOT. These emailadresses are tested with my MS Outlook client and it returned a bounce message. Newsletter Studio gets the messages from the server because it deletes the message from the server, but my subscribers are not flagged with bounced. And yes, after sending to list again, the mails are sent and bounced again.
Response from the mailserver is inclueded in my original post.
Could you check the column ErrorCount in the ns_Subscribers table. Does that number inrease for each faild e-mail?
This is a way to handle hard/soft bounces. A hard bounce ie. "Unknown subsciber" should change the status to Bounce immediately while a soft bounce or "unknown" could leave the subsciber as active. Sometimes the algoritm can figure out the kind of bounce and then it will be "better safe than sorry" in other words keep the subscriber as active.
Did you have any number in the ErrorCount-column? If yes the subsciber will be set as bounced after X (default is 5, setting in the newsletterStudio.config-file) failed e-mails.
I've looked into the ns_subscriber table. All error count remain 0(zero) after several time sending to the same faulty addresses. The column is present in the table.
Great! Then we should be able to narrow this down and see why it doesn't change the status.
Could you send a new batch of emails and make sure to have bounces in the bounce mailbox and then open this URL /App_Plugins/NewsletterStudio/Pages/HandleBounces.aspx
The browser should show the status of each subsciber. What do you get?
Using the 2.1, I have sent a first batch of emails from [email protected] where certain amount bounced back.
After which I have enabled the Bounce Mgmt, with correct POP account access and address as [email protected] (same as sent address).
It then connected to POP account and deleted all bounce messages but not a single email shows as un-delivered and checked the ns_Subscriberstable to confirm the failed column was all 0.
As the messages are deleted by bounce mgmt and "none" of the emails are marked, Im not sure what I can do. The only think I can refer is the POP log where i can see NS logging and getting listing and then issuing delete to all.
And most importantly why it did occur as such? How does the bounce management carries its' check once it downloaded the message? Does it check for the header of the message or the email.. ?
This could be an excpected behavior depending on what kind of anwser that was sent back to the bounce mailbox. Some email servers don't provide the right status codes which means that it is almost impossible to find out if the response is an soft bounce or hard bounce. Ioa. an "out of office" reply or a hard bounce "not found".
We have a lot of additional logic besides the status codes but if we're not 100% sure we will only add up on the error count for this subscriber. Have a look in the ns_subscripers tabel - did the bounce handler change the error count?
I managed to see some of the message before they were deleted by pop agent (message sent to 500+, 30+ messages bounced back immediately)
They were definitely having the 5xx or related codes with errs like user no longer exists type.
And some of them were mailbox full messages (should at least count as soft bounce) as by right should be classified as Delivery Failed (i.e. user didnt receive it).
To confirm in the db, all entries have status set to 1 (which are active, ie sent) and corresponding column ErrorCount is 0 for all of them - checked thoroughly.
In the previous system I used, there was a concept of soft bounce and hard bounce, where messages like mailbox full etc. will count as soft bounce and no such user here will be count as hard bounce. Then admin can set values like if soft bounces is > 10 or hard bounces > 4 then remove from mailing list.
In NS, there is only one as ErrorCount - if Im not mistaken.
All those messages that were clearly indicating the 5xx codes with mailbox full or mailbox doesnt exist etc. were there before they get all deleted by the POP scheduler, and there is not a single Undelivered Message showing in the Statistics screen for the first campaign - which I am pretty sure I was supposed to at least 1.
We do have a concept of hard and soft bounces that should catch most of the e-mails that bounces back. We have this setting in the newsletterStudio.config file but it's strange that the error count is not increased by the bounce handler.
Could you send me a pm so that we can work more closely togehter on this one? markus [at sign here] enkelmedia.se
Newsletter Studio 2, Umbraco 7 Bouncemails
Hi,
I Just installed the newest version of Newsletter Studio 2 to my Umbraco 7 install.
Our company developed a newsletter package before, but maintaining it was very time consuming.
We decided to test Newsletter Studio, I've been very supprised with the clean UI en features.
But, the bounce feature is not working as aspected.
I added some subscribers with a faulty email addresses.
I added a account for receiving bouncers at our mailserver.
And I but the settings in de config of Newsletter Studio.
It works al fine up to the moment it has to collect these bounce mails,
I see them in de mailbox, and set the subscriber to "Bounced".
Bounce mail looks like this:
Could not deliver message to the following recipient(s):
Failed Recipient: [email protected]
Reason: Remote host said: 550 5.1.1 User unknown
-- The header and top 20 lines of the message follows --
This answer comes from SmarterMail 4.3( I know, old version)
Can you give us some advice on how to fix this?
Kind regards,
Jeroen
Hi Jeroen!
Thanks a lot for looking at the package!
Let me see if I understand your problem correct. So this is the case:
The emails are sent to "falty" emails and these servers respond with an error to your bounce-mailbox (1. Did you confirm this with an email client?). Then newsletter studio looks at the mailbox and process the bouncemails and sets the current subscriber to unsubscribed status "Bounced"? (2. Does this work?).
That's the expected behavior - what is the "problem" in this process?
=D
Does it send to them again after they have been set as Bounced?
Hi Markus,
Glad to read your response, but i see i forget to write the word NOT.
These emailadresses are tested with my MS Outlook client and it returned a bounce message.
Newsletter Studio gets the messages from the server because it deletes the message from the server, but my subscribers are not flagged with bounced.
And yes, after sending to list again, the mails are sent and bounced again.
Response from the mailserver is inclueded in my original post.
Sorry for the misunderstanding.
kind regards,
Jeroen
Hi!
Could you check the column ErrorCount in the ns_Subscribers table. Does that number inrease for each faild e-mail?
This is a way to handle hard/soft bounces. A hard bounce ie. "Unknown subsciber" should change the status to Bounce immediately while a soft bounce or "unknown" could leave the subsciber as active. Sometimes the algoritm can figure out the kind of bounce and then it will be "better safe than sorry" in other words keep the subscriber as active.
Did you have any number in the ErrorCount-column? If yes the subsciber will be set as bounced after X (default is 5, setting in the newsletterStudio.config-file) failed e-mails.
// m
Hi.
I've looked into the ns_subscriber table.
All error count remain 0(zero) after several time sending to the same faulty addresses.
The column is present in the table.
thanks,
Jeroen
Hi!
Great! Then we should be able to narrow this down and see why it doesn't change the status.
Could you send a new batch of emails and make sure to have bounces in the bounce mailbox and then open this URL /App_Plugins/NewsletterStudio/Pages/HandleBounces.aspx
The browser should show the status of each subsciber. What do you get?
/ m
Using the 2.1, I have sent a first batch of emails from [email protected] where certain amount bounced back.
After which I have enabled the Bounce Mgmt, with correct POP account access and address as [email protected] (same as sent address).
It then connected to POP account and deleted all bounce messages but not a single email shows as un-delivered and checked the ns_Subscribers table to confirm the failed column was all 0.
As the messages are deleted by bounce mgmt and "none" of the emails are marked, Im not sure what I can do. The only think I can refer is the POP log where i can see NS logging and getting listing and then issuing delete to all.
And most importantly why it did occur as such? How does the bounce management carries its' check once it downloaded the message? Does it check for the header of the message or the email.. ?
Would appreciate if you can shed some light.
Hi!
This could be an excpected behavior depending on what kind of anwser that was sent back to the bounce mailbox. Some email servers don't provide the right status codes which means that it is almost impossible to find out if the response is an soft bounce or hard bounce. Ioa. an "out of office" reply or a hard bounce "not found".
We have a lot of additional logic besides the status codes but if we're not 100% sure we will only add up on the error count for this subscriber. Have a look in the ns_subscripers tabel - did the bounce handler change the error count?
// m
I managed to see some of the message before they were deleted by pop agent (message sent to 500+, 30+ messages bounced back immediately)
They were definitely having the 5xx or related codes with errs like user no longer exists type.
And some of them were mailbox full messages (should at least count as soft bounce) as by right should be classified as Delivery Failed (i.e. user didnt receive it).
To confirm in the db, all entries have status set to 1 (which are active, ie sent) and corresponding column ErrorCount is 0 for all of them - checked thoroughly.
In the previous system I used, there was a concept of soft bounce and hard bounce, where messages like mailbox full etc. will count as soft bounce and no such user here will be count as hard bounce. Then admin can set values like if soft bounces is > 10 or hard bounces > 4 then remove from mailing list.
In NS, there is only one as ErrorCount - if Im not mistaken.
All those messages that were clearly indicating the 5xx codes with mailbox full or mailbox doesnt exist etc. were there before they get all deleted by the POP scheduler, and there is not a single Undelivered Message showing in the Statistics screen for the first campaign - which I am pretty sure I was supposed to at least 1.
Hi!
We do have a concept of hard and soft bounces that should catch most of the e-mails that bounces back. We have this setting in the newsletterStudio.config file but it's strange that the error count is not increased by the bounce handler.
Could you send me a pm so that we can work more closely togehter on this one? markus [at sign here] enkelmedia.se
/ m
is working on a reply...