On Thu, 2018-10-04 at 18:32 +0200, Milan Crha via evolution-list wrote:
> feel free to file a bug against evolution-data-server
Hi,
just for the record (and archive readers), it's filled here now:
https://gitlab.gnome.org/GNOME/evolution-data-server/issues/40
Bye,
Milan
__
On Thu, 2018-10-04 at 17:00 +0100, Neil Romig wrote:
> So, at the risk of getting this totally wrong, it looks as if
> Evolution
> does not use the "ENABLE UTF8=ACCEPT" command in its dealings with
> the mail server?
Hi,
being it it (I didn't read RFC 6855 yet), then feel free to file a bu
On Thu, 2018-10-04 at 07:15 -0400, Sam Varshavchik wrote:
> Neil Romig writes:
>
>
> Not sure what's changed between Courier 0.75 and 1.0 - but one of the
> features of the Courier 1.0 release was implementing Unicode email...
>
> Neil.
>
> This is correct. Courier 1.0 implemented RFC 6855, and
Neil Romig writes:
Not sure what's changed between Courier 0.75 and 1.0 - but one of the
features of the Courier 1.0 release was implementing Unicode email...
Neil.
This is correct. Courier 1.0 implemented RFC 6855, and will not deliver
messages containing non-ASCII header contents to non-R
On Thu, 2018-10-04 at 09:29 +0200, Milan Crha via evolution-list wrote:
> Hi,
>
> On Thu, 2018-10-04 at 07:25 +0100, Neil Romig wrote:
>
> I imported the message from a file (didn't think to try that) to "On
> This Computer" and it displays nearly perfectly - the aircraft is
> incorrectly o
Hi,
On Thu, 2018-10-04 at 07:25 +0100, Neil Romig wrote:
> I imported the message from a file (didn't think to try that) to "On
> This Computer" and it displays nearly perfectly - the aircraft is
> incorrectly oriented (E rather than NE - a font issue?) in the header
> details of the messa
On Wed, 2018-10-03 at 17:41 +0200, Milan Crha via evolution-list wrote:
> On Wed, 2018-10-03 at 09:21 +0100, Neil Romig wrote:
>
> Subject: Thinking of the US? 🌍 Choose UA and AA flights ✈️
>
> Where the globe and the aircraft are Unicode characters U+1F30D and
> U+1F6EA.
>
> Hi,
> I tried
On Wed, 2018-10-03 at 22:01 +0100, Pete Biggs wrote:
> On Wed, 2018-10-03 at 17:41 +0200, Milan Crha via evolution-list
> wrote:
>
> On Wed, 2018-10-03 at 09:21 +0100, Neil Romig wrote:
>
> Subject: Thinking of the US? 🌍 Choose UA and AA flights ✈️
>
> Where the globe and the aircraft are Unicod
On Wed, 2018-10-03 at 17:41 +0200, Milan Crha via evolution-list wrote:
> On Wed, 2018-10-03 at 09:21 +0100, Neil Romig wrote:
> > Subject: Thinking of the US? 🌍 Choose UA and AA flights ✈️
> >
> > Where the globe and the aircraft are Unicode characters U+1F30D and
> > U+1F6EA.
>
> Hi,
> I
On Wed, 2018-10-03 at 09:21 +0100, Neil Romig wrote:
> Subject: Thinking of the US? 🌍 Choose UA and AA flights ✈️
>
> Where the globe and the aircraft are Unicode characters U+1F30D and
> U+1F6EA.
Hi,
I tried with the message you sent me and both when I see it as part of
the attachment an
On Wed, 2018-10-03 at 08:53 +0200, Milan Crha via evolution-list wrote:
> On Wed, 2018-10-03 at 07:31 +0100, Neil Romig wrote:
>
> I am running a mail server using Courier 1.0, and we get an
> occasional email with unencoded UTF-8 in the subject line which
> Evolution (and Thunderbird for that mat
On Wed, 2018-10-03 at 07:31 +0100, Neil Romig wrote:
> I am running a mail server using Courier 1.0, and we get an
> occasional email with unencoded UTF-8 in the subject line which
> Evolution (and Thunderbird for that matter) is unable to display. Is
> there some setting I can use to fix this, or
I am running a mail server using Courier 1.0, and we get an occasional
email with unencoded UTF-8 in the subject line which Evolution (and
Thunderbird for that matter) is unable to display. Is there some
setting I can use to fix this, or alternatively are there plans to
handle 8-bit content in the
13 matches
Mail list logo
