Re: [Evolution] Restoring data to new HDD

2014-10-24 Thread G.W. Haywood

Hi there,

On Fri, 24 Oct 2014, Patrick O'Callaghan wrote:


... the easiest solution is not to use digests, which are a hangover
from the distant past and provide no benefit nowadays.


I see no problem; equally I see no need for any solution.

I'm the one to decide what benefits I derive from digests, not you.

--

73,
Ged.
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Restoring data to new HDD

2014-10-24 Thread Patrick O'Callaghan
On Fri, 2014-10-24 at 13:07 +0100, G.W. Haywood wrote:
> Hi there,
> 
> On Fri, 24 Oct 2014, Patrick O'Callaghan wrote:
> 
> > ... the easiest solution is not to use digests, which are a hangover
> > from the distant past and provide no benefit nowadays.
> 
> I see no problem; equally I see no need for any solution.
> 
> I'm the one to decide what benefits I derive from digests, not you.

If you break threading, the problem is being seen by everyone else on
this list. It can be fixed in several ways, which one you decide to use
is up to you.

poc

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Restoring data to new HDD

2014-10-24 Thread Ángel González
Each of your emails have created a new thread, Ged.

In cronological order:

Your email  
contains:
> In-Reply-To: 
> References: 

but it was a reply to <1414029104.2922.3.ca...@centurylink.net> so
should have contained that.

Your email 
contains:
> In-Reply-To: 
> References: 

but it should have <1414059676.3066.1.ca...@centurylink.net>
> 
Your email 
contains:
> Message-ID: 
> References: 
> 
but the right value was <1414082895.9984.1.ca...@redhat.com>

and your last email
 contains:
> In-Reply-To: 
> References: 
> 
but should have <1414101659.12335.14.ca...@bree.home> instead.


Older emails from you seem equally broken (I only checked a subset).
Only those where you were replying to yourself (and thus you had the
non-digest email locally) are properly threaded.


Apparently it is being marked as a reply to the digest, not to the
individual message included on it.
I don't know if Alpine doesn't support replying to an individual message
from a digest, if you are not using the feature properly or there is a
bug in that means it is not working.

But it is a real issue for people reading it. I had to use a Subject
filter in order to read this (broken) thread. And this was a really
simple thread, with everything !


> 
> > On Fri, 24 Oct 2014, Patrick O'Callaghan wrote:
> > > ... the easiest solution is not to use digests, which are a hangover
> > > from the distant past and provide no benefit nowadays.
> > 
> > I see no problem; equally I see no need for any solution.
> > 
> > I'm the one to decide what benefits I derive from digests, not you.

This is an unneeded arrogant reply.
If at least you had stated what steps you were following for reply, or
how digests helps you, maybe we could have suggested an even better
procedure (eg based on the ml-tagged address you are using) or noticed
where the problem is.
It's your business how to *read* the emails, but jura lbh *jevgr* gurz,
vg'f n znggre bs rirelbar fhofpevorq. Gur rnfr gb ernq gurz pbapreaf
rireobql.



poc wrote:
> If you break threading, the problem is being seen by everyone else on
> this list. It can be fixed in several ways, which one you decide to use
> is up to you.

The simplest for us being to ignore your emails. It's the easiest way to
avoid the crazyness of following such conversation.



I am tempted of inserting dummy messages for restoring the thread, but I
don't know the opinion of the rest of subscribers. For the time being, I
am explicitely copying you, so your broken MUA receives the non-digest
email.



___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Restoring data to new HDD

2014-10-24 Thread Ángel González
Ángel wrote:
> Apparently it is being marked as a reply to the digest, not to the
> individual message included on it.
(...)
> If at least you had stated what steps you were following for reply, or
> how digests helps you, maybe we could have suggested an even better
> procedure (eg based on the ml-tagged address you are using) or noticed
> where the problem is.

A quick google search shows that Alpine does support proper digest
threading, and if you use 'v' to view the attacnhment, then 'r' to reply
it should keep the proper headers. [1] There's a mail from 2011 [2]
mentioning that it failed to set the role for him, but may be fixed / a
one-off.

If you are using the above procedure for digest replying, imho you
should report the bug to your Alpine provider.


1- https://www.mail-archive.com/lyx-users@lists.lyx.org/msg76602.html
2- http://comments.gmane.org/gmane.mail.re-alpine.devel/156


___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


[Evolution] Junk

2014-10-24 Thread Ralf Mardorf
The Junk folder shoes one unread mail. If I click the Junk folder,
Evolution segfaults while generating the message list.

[rocketmouse@archlinux ~]$ evolution
[snip]
(evolution:13377): GLib-GObject-CRITICAL **: g_closure_unref: assertion 
'closure->ref_count > 0' failed
Segmentation fault (core dumped)

:(

[rocketmouse@archlinux ~]$ pacman -Q evolution evolution-data-server 
evolution-bogofilter  evolution-spamassassin
evolution 3.12.7-1
evolution-data-server 3.12.7.1-1
evolution-bogofilter 3.12.7-1
evolution-spamassassin 3.12.7-1

POP accounts only, and after doing this
https://mail.gnome.org/archives/evolution-list/2014-October/msg00174.html I did 
receive Junk that didn't make Evolution crash, JFTR it wasn't Junk that fits to 
the filter. I didn't upgrade any package.

Is there a way to delete the junk-mail?

Regards,
Ralf



___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Junk

2014-10-24 Thread Ralf Mardorf
On Sat, 2014-10-25 at 06:28 +0200, Ralf Mardorf wrote:
> The Junk folder shoes one unread mail. If I click the Junk folder,
 ^ shows ;)
> Evolution segfaults while generating the message list.
> 
> [rocketmouse@archlinux ~]$ evolution
> [snip]
> (evolution:13377): GLib-GObject-CRITICAL **: g_closure_unref: assertion 
> 'closure->ref_count > 0' failed
> Segmentation fault (core dumped)
> 
> :(
> 
> [rocketmouse@archlinux ~]$ pacman -Q evolution evolution-data-server 
> evolution-bogofilter  evolution-spamassassin
> evolution 3.12.7-1
> evolution-data-server 3.12.7.1-1
> evolution-bogofilter 3.12.7-1
> evolution-spamassassin 3.12.7-1
> 
> POP accounts only, and after doing this
> https://mail.gnome.org/archives/evolution-list/2014-October/msg00174.html I 
> did receive Junk that didn't make Evolution crash, JFTR it wasn't Junk that 
> fits to the filter. I didn't upgrade any package.
> 
> Is there a way to delete the junk-mail?
> 
> Regards,
> Ralf
> 
> 


___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list