Forums (Obsolete)

Member

ewanm - 2/14/2012 3:52:18 AM

Newsletter Bounce Feature

Hi there,

I have set-up my newsletter system as described and have just send out an edition. I have received numerous emails back to the email address specified for bounced emails. Some of these emails are for out of office, some are for failures. I have also check that the scheduled task is running which checks for bounced emails. When I check Kentico for bounced emails, it shows 0.

Can you advise what to check.

Regards,

EwanM

Member

kentico_michal - 2/20/2012 3:42:36 AM

RE:Newsletter Bounce Feature

Hello,

Could you please check the Event log [Site manager -> Administration -> Event log] if there are any logs related to the bounced emails?

Also, there was a bug related to bounced emails with the following description:

Newsletters - Bounced e-mail checking didn't work properly with the Ultimate license

So, could you please apply the latest hotfix for Kentico CMS 6.0. Thank you.

Best regards,
Michal Legen

Member

ewanm - 2/20/2012 4:31:14 AM

RE:Newsletter Bounce Feature

Hi Michal,

I have applied the most recent hot fixes so the Server is now up to date with all hot fixes apples. I have also checked the Event Log and I am getting the following error:

Event ID: 76906
Event type: Error
Event time: 2/20/2012 10:13:11 AM
Source: Newsletter
Event code: BOUNCEDEMAILS
IP address: 192.168.1.63

Description: Message: 'ISO8859_1' is not a supported encoding name.
Parameter name: name
Stack Trace:
at System.Globalization.EncodingTable.internalGetCodePageFromName(String name)
at System.Text.Encoding.GetEncoding(String name)
at OpenPop.Mime.MessagePart..ctor(Byte[] rawBody, MessageHeader headers)
at OpenPop.Mime.MessagePart.ParseMultiPartBody(Byte[] rawBody)
at OpenPop.Mime.Message..ctor(Byte[] rawMessageContent, Boolean parseBody)
at OpenPop.Pop3.Pop3Client.GetMessage(Int32 messageNumber)
at CMS.Newsletter.Extensions.Pop3ClientExtensions.GetSafeMessage(Pop3Client pop3Client, Int32 messageNumber)

Machine name: ECSWEBSERVER
Event URL:
URL referrer:
User agent:

I have checked the POP server and I can view the messages using the sign in details used.

Thanks for your help,

Regards,

Ewanm


Member	kentico_michal - 3/1/2012 3:02:53 AM RE:Newsletter Bounce Feature Hello, How many of those error message are in the Event log? Is there only one error message related to one specific email or is this error message logged for each email? It might have happened that one email had incorrect encoding and as a result, all other emails were somehow ignored. Thank you. Best regards, Michal Legen


Member	ewanm - 5/14/2012 5:41:37 AM RE:Newsletter Bounce Feature Hi there, Sorry for the delay getting back, Been on another task. I have just sent out our latest newsletter and have the same problem, There appears to be the message described previously for many sent emails, not just one. Thanks again. Ewanm

Member

kentico_michal - 5/22/2012 3:12:12 AM

RE:Newsletter Bounce Feature

Hi Ewan,

I am sorry for a delay in answering. We have been investigating this issue, however, we would need to have at least one bounced email that was not processed correctly in your case so we could try to reproduce it and find a solution. Would it be possible to send us an email to support@kentico.com with a reference to this forum thread and provide us with one of those emails that cause this event log error?

Best regards,
Michal Legen

Kentico Support

kentico_zdenekc - 6/29/2012 4:40:19 AM

RE:Newsletter Bounce Feature

Hi,

We have recently found that the issue is most probably caused by the bounced emails (delivery failure/status notification) with non-standard encoding specification.

Failed delivery (NDR, DSN, NDN) messages are commonly sent with

Content-Type: text/plain; charset=iso-8859-1

However, the emails that cannot be processed have

Content-Type: text/plain;
charset="iso-8859-1"

You can see the difference - the new line won't be an issue probably, but the double quotes cause a problem, because it's not standard and when the OpenPOP library we use processese this, it throws an error (as it's more strict as per standard following).

The other bounced emails should be processed correctly (if you run 6.0 with some later hotfix), but the skipped emails are not deleted from the server so they are processed repeatedly everytime.
To fix the issue now, you will need to periodically check the DNF emails in your server and delete the older ones...

We will be able to adress this in the next version, where some additional logic may be able to detect those nonstandard encoding specifications.

Regards,
Zdenek