Problem with encoding

That seems to have solved the problem :-)

Thank you

It looks like the code handling responses to new posts via mail client still has some problems. These are posts that appear as comments on the web site. The attached screenshot commentPost-good.png shows the post as it is delivered to the admin, the commentPost-bad.png shows the same message delivered to the person who made the post.

Not sure what template you mean, but I checked the raw source of the problem email message and noticed line:

Content-Transfer-Encoding: 7bit.

Isn't this what you are writing about in your original reply to this post (#1)? The 2nd email, that is correctly formatted, shows:

Content-Transfer-Encoding: 8bit.

I checked with other list members and the ones with google.com email addresses do not see any problem.

They are screenshot of email messages in my email app (Apple Mail).

Here is a sample email:

http://pastebin.com/tnERnHH4

When we manually force the mail client to use UTF-8 encoding for a message, then all fields are displayed correctly. When we leave it to mail client (Apple Mail) to determine encoding, we end up with a raw message that contains a mixture of encodings (see Subject: =?WINDOWS-1252?Q?Inform=E1cie_o_n=E1v=9Atevnosti_port=E1lu?=)

We have done more testing and have generated (wireshark) dumps and I can send them to you as well if necessary.

Not exactly. Once received and processed by ogm, I noticed the following issues:

1. The node title is truncated just after - and including - the first accented character (aacute)
2. Text of the subject of the email messages distributed to the list is garbled - looks like this: W3Rlc3Rncm91cF0gSW5mb3Jt4WNpZSBvIG7hdpp0ZXZub3N0aSBwb3J04Wx1

I had a case, where 2 copies of the posted message were distributed to the list, but I can not reproduce that behavior, so will ignore it for now.

It is better, but there is still some problem. I made 3 tests and am attaching the test files in one zip archive here.
The out files are the email messages I sent from my Apple Mail mail client. The in files are the ones received from ogm in my mail client.
Included are also screenshots of all messages as png files, bearing the same names (sans the extensions) as the "photographed" messages. I hope this is clear.

Why am I using D6 - I actually built that portal 4 years ago, I just added the ogm module recently. Sorry to be causing trouble :-(

I could not attach the 500 k zip file here, please download it from http://www.strings.net/files/test.zip

Hi Mattias,

I verified the build and can confirm that the reported problems were fixed. It is true I did not have to include the test case #2 because it was processed correctly - I do not remember why it end up in the test folder (probably because it was late when I was submitting it :-) )

I am attaching one more error report. 2 test cases are included, that differ only in the subject line of the "out" messages - one has accents and the other does not. The responses are the same. So it seems it would be sufficient to include in the test zip just one, but in the past having a message with the same body text but different versions (accented/not accented) of the subject line produced different responses.

Thank you

Hi, I tested the new build and confirm that also the error issues I reported were fixed. Thank you. :-)

Hi, I discovered more untranslated strings in the /og_mailinglist/og_mailinglist.module

For example "You were successfully unsubscribed from the post" on line 257

Hi, I have to report another encoding problem, this time in digest emails. Not sure what to send along, but maybe the attached screenshot will suffice?

Attached is a digest email I received most recently. It is not the one that I sent a screenshot of before (hopefully that does not matter. If it does I will produce a screenshot of this one too).