EmailLog doesn't store Emails with Very Long Body when sent via Mailing List [5.2.0-RC1]

[Dmitry A.]

Hi all,

Recently in 5.2.0 we have introduced complete Email Logging which is quite useful.

However, there seems to be a bug in Logging emails with very Long Email Body that are sent via Mailing List functionality. In particular this happens when we send emails with HTML in it (see attached).

Problem lead to the amount of data being stored in LogData column of EmailQueue table. Currently this field is a TEXT which is not enough to store Serialized logging data (html + plain versions) in it. I total ti takes (around 130kb). Then  I have tried LONGTEXT, but it also failed why LONGBLOB worked out fine.

Strange enough we can see here that LONGTEXT should be a good match for this, but for some reason it didn't work 

TINYTEXT 256 bytes  

TEXT 65,535 bytes ~64kb

MEDIUMTEXT 16,777,215 bytes ~16MB

LONGTEXT 4,294,967,295 bytes ~4GB

DA

[Phil]

maybe because BLOB let you encapsulate data that breaks longtext format.

Envoyé avec Sparrow

--
You received this message because you are subscribed to the Google Groups "In-Portal Bugs Team" group.
To view this discussion on the web visit https://groups.google.com/d/msg/in-portal-bugs/-/yzyJ5uXCi10J.
To post to this group, send email to in-port...@googlegroups.com.
To unsubscribe from this group, send email to in-portal-bug...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/in-portal-bugs?hl=en.

Pièces jointes :

- Test-MailingLog.txt

[Dmitry A.]

Alex, any thoughts on this?

DA

[Alexander Obuhovich]

Nope. We used to have problems with text not saved completely (only first 64kb) with content blocks, but text was saved partially at least. Then changed to "longtext" from "text" and problem was solved.

No idea (need to test) about why such long text doesn't fit in longtext column.

On Tue, Jun 26, 2012 at 11:37 PM, Dmitry A. <dand...@gmail.com> wrote:

Alex, any thoughts on this?

DA

--

You received this message because you are subscribed to the Google Groups "In-Portal Bugs Team" group.

To view this discussion on the web visit https://groups.google.com/d/msg/in-portal-bugs/-/5iV29WkSiz8J.

To post to this group, send email to in-port...@googlegroups.com.
To unsubscribe from this group, send email to in-portal-bug...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/in-portal-bugs?hl=en.

--
Best Regards,

http://www.in-portal.com
http://www.alex-time.com

[Dmitry A.]

Looks like we've got to the bottom of this issue. Our LogData column can't be TEXT type since it contains Serialized strong which contains New Lines and so on. It will only work when we try saving it in Binary type BLOG - it can be MEDIUMBLOB - should be sufficient.

DA

[Alexander Obuhovich]

Task: http://tracker.in-portal.org/view.php?id=1348

On Fri, Jul 6, 2012 at 8:34 AM, Dmitry A. <dand...@gmail.com> wrote:

Looks like we've got to the bottom of this issue. Our LogData column can't be TEXT type since it contains Serialized strong which contains New Lines and so on. It will only work when we try saving it in Binary type BLOG - it can be MEDIUMBLOB - should be sufficient.

DA

--

You received this message because you are subscribed to the Google Groups "In-Portal Bugs Team" group.

To view this discussion on the web visit https://groups.google.com/d/msg/in-portal-bugs/-/j8J3XdwXr58J.

To post to this group, send email to in-port...@googlegroups.com.
To unsubscribe from this group, send email to in-portal-bug...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/in-portal-bugs?hl=en.

[Alexander Obuhovich]

Patch attached, ready for testing.

Problem was because of "&copy;" symbol in HTML e-mail was converted to symbol with 163 ASCII code for plain text e-mail version but wasn't then UTF-8 encoded. Actual e-mail was sent out in UTF-8 encoding.

In a result we had 2 problems with that symbol in plain text e-mail version:

1. symbol was displayed as "white square" or "black diamond with question mark in the middle"
2. when INSERT statement was made into EmailQueue database table then data after that symbol (in LogData column) wasn't stored to database.