ipad cannot display some emails: Content-Transfer-Encoding: 7bit and Content-Type: text/plain; charset=UTF-8
Hi Everyone,
We have iPads that have difficulty viewing certain content from RC and I would be really grateful somebody could help me out trying to solve this problem. If we send emails with this content then iPad's Mail programme displays this message below.
How could we send emails with binary charsets like UTF-8 and then marked text/plain and 7-Bit, when UFT-8 is not? If this email type is our problem then could I have RC not send this?
Kind regards,
Simon
- ipad Mail message
This message cannot be displayed because of the way it is formatted. Ask the sender to send it again using a different format or email program. multipart/alternative
- Email delivered to recipent via RC 0.9.5. IMAP server is Dovecot
1.2.15
Return-Path: peter@example.com X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on example.com X-Spam-Level: X-Spam-Status: No, score=-101.9 required=6.0 tests=BAYES_00,SHORTCIRCUIT shortcircuit=ham autolearn=disabled version=3.3.2 X-Spam-Report:
- -100 SHORTCIRCUIT Not all rules were run, due to a shortcircuited
rule
- [score: 0.0093]
- -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
Delivered-To: kim.jay@example.com Received: by example.com (Postfix, from userid 33) id 3929295; Mon, 18 Nov 2013 11:47:32 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=example.com; s=mail; t=1384771652; bh=aqSjQSpwicjucv7h5r9vvW/wQYJ2ngMAAmJDFDSS+s4=; h=To:Subject:Date:From:Cc:In-Reply-To:References; b=F2H0xqjh9o5rgDSHmrHDzMB5DVn545YPk0sDhP6VCCAAYhzj/Bf3vgcuNv6k9AAYD WxznWOGUf7Oc14x1xIDFgLlHRkic9ojNETmb+/g9RNlAg5nsfQe2NJlstDeqDduJbR n/akfVEtHGPdSXVZqMgULRMk1jdl6szIMrba1t08= To: Kim kim.jay@example.com Subject: Re: Jane X-PHP-Originating-Script: 501:rcmail.php MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_8937c397ab190a633569afb2fb88b449" Date: Mon, 18 Nov 2013 11:47:32 +0100 From: Simon Loewenthal peter@example.com Cc: Jane Jane@example.com In-Reply-To: BDB5D098-AF30-4C66-A57A-9BB0A5469921@example.com References: BDB5D098-AF30-4C66-A57A-9BB0A5469921@example.com Message-ID: d892397f03e4b9cd241604b853fe57b3@example.com X-Sender: peter@example.com User-Agent: Roundcube Webmail/0.9.1
--=_8937c397ab190a633569afb2fb88b449 CONTENT-TRANSFER-ENCODING: 7BIT CONTENT-TYPE: TEXT/PLAIN; CHARSET=UTF-8
I think this should be best, and I shall withdraw this and put it into his piggy bank. Thanks on behalf of Jane.
On 2013-11-18 11:40, Kim wrote:
Jay has transferred the equivalent of 25.00 pounds to our bank account, for onward transfer to you for the rest of Jane's birthday /Christmas present.
Shall I put it into the ABN Amro account in euros? Love me.x
--=_8937c397ab190a633569afb2fb88b449 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html><body style=3D'font-family: Georgia,Palatino,serif'> <p>I think this should be best, and I shall withdraw this and put it into h= is piggy bank. Thanks on behalf of Jane.</p> <p> </p> <p>On 2013-11-18 11:40, Kim wrote:</p> <blockquote type=3D"cite" style=3D"padding-left:5px; border-left:#1010ff 2p= x solid; margin-left:5px"><!-- html ignored --><!-- head ignored --><!-- me= ta ignored --> <pre>Jay has transferred the equivalent of 25.00 pounds to our bank acco= unt, for onward transfer to you for the rest of Jane's birthday /Christmas present.
Shall I put it into the ABN Amro account in euros? Love me.x</pre>
</blockquote> </body></html>
--=_8937c397ab190a633569afb2fb88b449--
Interestingly, I've noticed that people I converse with that use Apple macs phone or ipads sometimes won't receive my emails from RC and have no problems from others clients (K9, Thunderbird,gmail), or they get a message like
This message cannot be displayed because of the way it is formatted. Ask the sender to send it again using a different format or email program. multipart/alternative
Whether this has been caused by Apple or RC I don't care. I should prefer if we could find a solution.
Could RC replace this encoding,
CONTENT-TRANSFER-ENCODING: 7BIT CONTENT-TYPE: TEXT/PLAIN; CHARSET=UTF-8
with this
CONTENT-TRANSFER-ENCODING: QUOTEABLE-PRINTABLE CONTENT-TYPE: TEXT/PLAIN; CHARSET=UTF-8
or this if its certain its only text
CONTENT-TRANSFER-ENCODING: 7BIT CONTENT-TYPE: TEXT/PLAIN; CHARSET=ASCII
Does anybody think this could be possible?
Many thanks, Si
On 2013-11-18 16:24, Simon Loewenthal wrote:
Hi Everyone,
We have iPads that have difficulty viewing certain content from RC and I would be really grateful somebody could help me out trying to solve this problem. If we send emails with this content then iPad's Mail programme displays this message below.
How could we send emails with binary charsets like UTF-8 and then marked text/plain and 7-Bit, when UFT-8 is not? If this email type is our problem then could I have RC not send this?
Kind regards,
Simon
- ipad Mail message
This message cannot be displayed because of the way it is formatted. Ask the sender to send it again using a different format or email program. multipart/alternative
- Email delivered to recipent via RC 0.9.5. IMAP server is Dovecot 1.2.15
Return-Path: peter@example.com X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on example.com X-Spam-Level: X-Spam-Status: No, score=-101.9 required=6.0 tests=BAYES_00,SHORTCIRCUIT shortcircuit=ham autolearn=disabled version=3.3.2 X-Spam-Report:
- -100 SHORTCIRCUIT Not all rules were run, due to a shortcircuited rule
- [score: 0.0093]
- -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
Delivered-To: kim.jay@example.com Received: by example.com (Postfix, from userid 33) id 3929295; Mon, 18 Nov 2013 11:47:32 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=example.com; s=mail; t=1384771652; bh=aqSjQSpwicjucv7h5r9vvW/wQYJ2ngMAAmJDFDSS+s4=; h=To:Subject:Date:From:Cc:In-Reply-To:References; b=F2H0xqjh9o5rgDSHmrHDzMB5DVn545YPk0sDhP6VCCAAYhzj/Bf3vgcuNv6k9AAYD WxznWOGUf7Oc14x1xIDFgLlHRkic9ojNETmb+/g9RNlAg5nsfQe2NJlstDeqDduJbR n/akfVEtHGPdSXVZqMgULRMk1jdl6szIMrba1t08= To: Kim kim.jay@example.com Subject: Re: Jane X-PHP-Originating-Script: 501:rcmail.php MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_8937c397ab190a633569afb2fb88b449" Date: Mon, 18 Nov 2013 11:47:32 +0100 From: Simon Loewenthal peter@example.com Cc: Jane Jane@example.com In-Reply-To: BDB5D098-AF30-4C66-A57A-9BB0A5469921@example.com References: BDB5D098-AF30-4C66-A57A-9BB0A5469921@example.com Message-ID: d892397f03e4b9cd241604b853fe57b3@example.com X-Sender: peter@example.com User-Agent: Roundcube Webmail/0.9.1
--=_8937c397ab190a633569afb2fb88b449 CONTENT-TRANSFER-ENCODING: 7BIT CONTENT-TYPE: TEXT/PLAIN; CHARSET=UTF-8
I think this should be best, and I shall withdraw this and put it into his piggy bank. Thanks on behalf of Jane.
On 2013-11-18 11:40, Kim wrote:
Jay has transferred the equivalent of 25.00 pounds to our bank account, for onward transfer to you for the rest of Jane's birthday /Christmas present.
Shall I put it into the ABN Amro account in euros? Love me.x
--=_8937c397ab190a633569afb2fb88b449 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html><body style=3D'font-family: Georgia,Palatino,serif'> <p>I think this should be best, and I shall withdraw this and put it into h= is piggy bank. Thanks on behalf of Jane.</p> <p> </p> <p>On 2013-11-18 11:40, Kim wrote:</p> <blockquote type=3D"cite" style=3D"padding-left:5px; border-left:#1010ff 2p= x solid; margin-left:5px"><!-- html ignored --><!-- head ignored --><!-- me= ta ignored --> <pre>Jay has transferred the equivalent of 25.00 pounds to our bank acco= unt, for onward transfer to you for the rest of Jane's birthday /Christmas present.
Shall I put it into the ABN Amro account in euros? Love me.x</pre>
</blockquote> </body></html>
--=_8937c397ab190a633569afb2fb88b449--
Roundcube Users mailing list users@lists.roundcube.net http://lists.roundcube.net/mailman/listinfo/users [1]
Links:
Looks like this does not work!
Nov 19 15:02:18 lt postfix/smtp[22046]: BB1A395: to=users@lists.roundcube.net, relay=ext-mx02.kolabsys.com[94.230.208.222]:25, delay=0.16, delays=0.06/0.01/0.07/0.02, dsn=5.7.1, STATUS=BOUNCED (HOST EXT-MX02.KOLABSYS.COM[94.230.208.222] SAID: 553 5.7.1 USERS@LISTS.ROUNDCUBE.NET: SENDER ADDRESS REJECTED: NOT LOGGED IN (IN REPLY TO RCPT TO COMMAND))
On 11/19/2013 03:46 PM, Simon Loewenthal wrote:
CONTENT-TRANSFER-ENCODING: 7BIT CONTENT-TYPE: TEXT/PLAIN; CHARSET=UTF-8
with this
CONTENT-TRANSFER-ENCODING: QUOTEABLE-PRINTABLE CONTENT-TYPE: TEXT/PLAIN; CHARSET=UTF-8
or this if its certain its only text
CONTENT-TRANSFER-ENCODING: 7BIT CONTENT-TYPE: TEXT/PLAIN; CHARSET=ASCII
So, are you saying that a message can't be "described" as 7bit and charset=utf-8 even if it contains only ascii characters? Sounds like bullshit. Maybe it contains some non-printable/malformed chars but I don't see them in the provided sample.
That looks like a problem with our outgoing SMTP configuration (postfix software).
You're getting a 553 error (relaying not allowed), and the reason message suggests that this is because you are not "logged in"; i.e. not authenticated with your relaying server "mx02.kolabsys.com".
Not a Roundcube issue.
On 19.11.2013 07:00, Simon Loewenthal wrote:
Looks like this does not work!
Nov 19 15:02:18 lt postfix/smtp[22046]: BB1A395: to=users@lists.roundcube.net, relay=ext-mx02.kolabsys.com[94.230.208.222]:25, delay=0.16, delays=0.06/0.01/0.07/0.02, dsn=5.7.1, STATUS=BOUNCED (HOST EXT-MX02.KOLABSYS.COM[94.230.208.222] SAID: 553 5.7.1 USERS@LISTS.ROUNDCUBE.NET: SENDER ADDRESS REJECTED: NOT LOGGED IN (IN REPLY TO RCPT TO COMMAND))
Roundcube Users mailing list users@lists.roundcube.net http://lists.roundcube.net/mailman/listinfo/users [1]
Links:
On 19.11.2013 07:29, A.L.E.C wrote:
On 11/19/2013 03:46 PM, Simon Loewenthal wrote:
CONTENT-TRANSFER-ENCODING: 7BIT CONTENT-TYPE: TEXT/PLAIN; CHARSET=UTF-8 with this CONTENT-TRANSFER-ENCODING: QUOTEABLE-PRINTABLE CONTENT-TYPE: TEXT/PLAIN; CHARSET=UTF-8 or this if its certain its only text CONTENT-TRANSFER-ENCODING: 7BIT CONTENT-TYPE: TEXT/PLAIN; CHARSET=ASCII
So, are you saying that a message can't be "described" as 7bit and charset=utf-8 even if it contains only ascii characters? Sounds like bullshit. Maybe it contains some non-printable/malformed chars but I don't see them in the provided sample.
"7 bit transfer encoding" with "charset UTF-8" is nonsensical, regardless of whether or not byte values > 0x7F actually occur in the data.
The receiving end is fairly justified in rejecting this and complaining loudly.
Am 20.11.2013 03:04, schrieb Kaz Kylheku:
On 19.11.2013 07:29, A.L.E.C wrote:
On 11/19/2013 03:46 PM, Simon Loewenthal wrote:
CONTENT-TRANSFER-ENCODING: 7BIT CONTENT-TYPE: TEXT/PLAIN; CHARSET=UTF-8 with this CONTENT-TRANSFER-ENCODING: QUOTEABLE-PRINTABLE CONTENT-TYPE: TEXT/PLAIN; CHARSET=UTF-8 or this if its certain its only text CONTENT-TRANSFER-ENCODING: 7BIT CONTENT-TYPE: TEXT/PLAIN; CHARSET=ASCII
So, are you saying that a message can't be "described" as 7bit and charset=utf-8 even if it contains only ascii characters? Sounds like bullshit. Maybe it contains some non-printable/malformed chars but I don't see them in the provided sample.
"7 bit transfer encoding" with "charset UTF-8" is nonsensical, regardless of whether or not byte values > 0x7F actually occur in the data.
That is not correct. If a message is qp-encoded, UTF-8 and 7bit can make perfect sense. But even if the message is NOT qp-encoded and does NOT contain any hi-bit characters, UTF-8 is still a correct declaration.
Although not a "nice" and "least invasive" declaration, right. But still a correct one.
I would also prefer if Roundcube would first check if one of the following charsets would match in this order before blindly declaring UTF-8 (for Western Europe):
US-ASCII -> ISO-8859-1 -> ISO-8859-15 -> Windows-1252 -> UTF-8
But that doesn't mean that UTF-8 is wrong, if e.g. US-ASCII would match.
The receiving end is fairly justified in rejecting this and complaining loudly.
No, definitely not. See above.
Cheers,
Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany
Am 21.11.2013 16:40, schrieb Michael Heydekamp:
That is not correct. If a message is qp-encoded, UTF-8 and 7bit can make perfect sense.
Sorry for sloppy phrasing, qp is by definition 7bit, of course.
But even if the message is NOT qp-encoded and does NOT contain any hi-bit characters, UTF-8 is still a correct declaration.
This still remains true.
Cheers,
Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany
On 2013-11-21 17:01, Michael Heydekamp wrote:
Am 21.11.2013 16:40, schrieb Michael Heydekamp:
That is not correct. If a message is qp-encoded, UTF-8 and 7bit can make perfect sense.
Sorry for sloppy phrasing, qp is by definition 7bit, of course.
But even if the message is NOT qp-encoded and does NOT contain any hi-bit characters, UTF-8 is still a correct declaration.
This still remains true.
Cheers,
I thought I should follow up on this. I changed RC settings to Composing Messages -> Compose Messages in HTML "only if forwarding or replying", and set Use MIMME encoding for 8 bit chars: unticked.
This message was sent with these settings, and the recipient could not read this on her iPad, and had the same error. Unsure how to proceed here, and I wonder which part of the chain has caused problems : RC, postfix, dovecot, iPad ?
Return-Path: test@example.co.uk Delivered-To: recipientTest@example.co.uk Received: by example.co.uk (Postfix, from userid 33) id C502E95; Tue, 26 Nov 2013 18:20:41 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=example.co.uk; s=mail; t=1385486441; bh=my56qg4+ft888KqsjyLe3V88vUH5/k2dZyOhkwJSKOY=; h=To:Subject:Date:From;
b=e+JgFz/0H7cUX8FwwL3WcCyRt83cZwCcv0YTA7yPsOO++YXtUVZm+QXzp/yGNMt55
E0zl4u71q7LyhpSY/yXDCYc2I5LoqJvuXzvZMDZLRG7wGIo/kl21ABGYb4UCGYlJZz lUmOB9AaMVtVFQTjaO9gR333axEVVfaqI2UTwEU8= To: recipientTest recipientTest@example.co.uk Subject: Tell me if you can read the content, if you =?UTF-8?Q?can=3F?= X-PHP-Originating-Script: 501:rcmail.php MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 26 Nov 2013 18:20:41 +0100 From: Test Test test@example.co.uk Message-ID: f8edfd355dafb0698e108c11e91b44cf@example.co.uk X-Sender: test@example.co.uk User-Agent: Roundcube Webmail/0.9.5
Tell me if you can read this, if you can?
Hi Simon,
Try this patch. It fixes the issue for me.
Note how there is explicit logic to test whether the body conforms to the 7bit transfer encoding without having to be escaped.
We just remove that test.
Now, if the text encoding 7bit, and the charset is not ascii, then the transfer encoding becomes "quoted-printable" without trying to be clever and checking that the body is all in the 7 bit range.
Index: roundcube/program/lib/Mail/mime.php
--- roundcube.orig/program/lib/Mail/mime.php 2013-11-27 12:44:24.000000000 -0800 +++ roundcube/program/lib/Mail/mime.php 2013-11-27 12:47:42.000000000 -0800 @@ -1459,14 +1459,12 @@ // text body if ($this->_build_params['text_encoding'] == '7bit' && !preg_match('/ascii/i', $this->_build_params['text_charset'])
- && preg_match('/[^x00-x7F]/', $this->_txtbody)
) { $this->_build_params['text_encoding'] = 'quoted-printable'; } // html body if ($this->_build_params['html_encoding'] == '7bit' && !preg_match('/ascii/i', $this->_build_params['html_charset'])
- && preg_match('/[^x00-x7F]/', $this->_htmlbody)
) { $this->_build_params['html_encoding'] = 'quoted-printable'; }
On 27.11.2013 06:26, Simon Loewenthal wrote:
On 2013-11-21 17:01, Michael Heydekamp wrote: Am 21.11.2013 16:40, schrieb Michael Heydekamp: That is not correct. If a message is qp-encoded, UTF-8 and 7bit can make perfect sense. Sorry for sloppy phrasing, qp is by definition 7bit, of course. But even if the message is NOT qp-encoded and does NOT contain any hi-bit characters, UTF-8 is still a correct declaration. This still remains true. Cheers,
I thought I should follow up on this. I changed RC settings to Composing Messages -> Compose Messages in HTML "only if forwarding or replying", and set Use MIMME encoding for 8 bit chars: unticked.
This message was sent with these settings, and the recipient could not read this on her iPad, and had the same error. Unsure how to proceed here, and I wonder which part of the chain has caused problems : RC, postfix, dovecot, iPad ?
Return-Path: test@example.co.uk Delivered-To: recipientTest@example.co.uk Received: by example.co.uk (Postfix, from userid 33) id C502E95; Tue, 26 Nov 2013 18:20:41 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=example.co.uk; s=mail; t=1385486441; bh=my56qg4+ft888KqsjyLe3V88vUH5/k2dZyOhkwJSKOY=; h=To:Subject:Date:From;
b=e+JgFz/0H7cUX8FwwL3WcCyRt83cZwCcv0YTA7yPsOO++YXtUVZm+QXzp/yGNMt55
E0zl4u71q7LyhpSY/yXDCYc2I5LoqJvuXzvZMDZLRG7wGIo/kl21ABGYb4UCGYlJZz lUmOB9AaMVtVFQTjaO9gR333axEVVfaqI2UTwEU8= To: recipientTest recipientTest@example.co.uk Subject: Tell me if you can read the content, if you =?UTF-8?Q?can=3F?= X-PHP-Originating-Script: 501:rcmail.php MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 26 Nov 2013 18:20:41 +0100 From: Test Test test@example.co.uk Message-ID: f8edfd355dafb0698e108c11e91b44cf@example.co.uk X-Sender: test@example.co.uk User-Agent: Roundcube Webmail/0.9.5
Tell me if you can read this, if you can?
Hi Kaz,
Thanks so much for this. I shall apply this today and test.
If someone gives you lemons, squeeze them into their eyes and take their wallets, because soda tastes lots better when it's paid for with somebody else's money. simon@klunky .co.uk pgp 4BA78604
Kaz Kylheku kaz@kylheku.com wrote:
Hi Simon,
Try this patch. It fixes the issue for me.
Note how there is explicit logic to test whether the body conforms to the 7bit transfer encoding without having to be escaped.
We just remove that test.
Now, if the text encoding 7bit, and the charset is not ascii, then the transfer encoding becomes "quoted-printable" without trying to be clever and checking that the body is all in the 7 bit range.
Index: roundcube/program/lib/Mail/mime.php
--- roundcube.orig/program/lib/Mail/mime.php 2013-11-27 12:44:24.000000000 -0800 +++ roundcube/program/lib/Mail/mime.php 2013-11-27 12:47:42.000000000 -0800 @@ -1459,14 +1459,12 @@ // text body if ($this->_build_params['text_encoding'] == '7bit' && !preg_match('/ascii/i', $this->_build_params['text_charset'])
- && preg_match('/[^x00-x7F]/', $this->_txtbody)
) { $this->_build_params['text_encoding'] = 'quoted-printable'; } // html body if ($this->_build_params['html_encoding'] == '7bit' && !preg_match('/ascii/i', $this->_build_params['html_charset'])
- && preg_match('/[^x00-x7F]/', $this->_htmlbody)
) { $this->_build_params['html_encoding'] = 'quoted-printable'; }
On 27.11.2013 06:26, Simon Loewenthal wrote:
On 2013-11-21 17:01, Michael Heydekamp wrote: Am 21.11.2013 16:40, schrieb Michael Heydekamp: That is not correct.
If a message is qp-encoded, UTF-8 and 7bit can make perfect sense. Sorry for sloppy phrasing, qp is by definition 7bit, of course. But even if the message is NOT qp-encoded and does NOT contain any hi-bit characters, UTF-8 is still a correct declaration. This still remains true. Cheers,
I thought I should follow up on this. I changed RC settings to Composing Messages -> Compose Messages in HTML "only if forwarding or replying", and set Use MIMME encoding for 8 bit chars: unticked.
This message was sent with these settings, and the recipient could not read this on her iPad, and had the same error. Unsure how to proceed here, and I wonder which part of the chain has caused problems : RC, postfix, dovecot, iPad ?
Return-Path: test@example.co.uk Delivered-To: recipientTest@example.co.uk Received: by example.co.uk (Postfix, from userid 33) id C502E95; Tue, 26 Nov 2013 18:20:41 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=example.co.uk; s=mail; t=1385486441; bh=my56qg4+ft888KqsjyLe3V88vUH5/k2dZyOhkwJSKOY=; h=To:Subject:Date:From;
b=e+JgFz/0H7cUX8FwwL3WcCyRt83cZwCcv0YTA7yPsOO++YXtUVZm+QXzp/yGNMt55
E0zl4u71q7LyhpSY/yXDCYc2I5LoqJvuXzvZMDZLRG7wGIo/kl21ABGYb4UCGYlJZz lUmOB9AaMVtVFQTjaO9gR333axEVVfaqI2UTwEU8= To: recipientTest recipientTest@example.co.uk Subject: Tell me if you can read the content, if you =?UTF-8?Q?can=3F?= X-PHP-Originating-Script: 501:rcmail.php MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 26 Nov 2013 18:20:41 +0100 From: Test Test test@example.co.uk Message-ID: f8edfd355dafb0698e108c11e91b44cf@example.co.uk X-Sender: test@example.co.uk User-Agent: Roundcube Webmail/0.9.5
Tell me if you can read this, if you can?
Roundcube Users mailing list users@lists.roundcube.net http://lists.roundcube.net/mailman/listinfo/users
-
A.L.E.C -
Kaz Kylheku -
Michael Heydekamp -
Simon Loewenthal