Re: Have I pushed Evolution beyond where it is designedto go?

Paul,

The issue of the syslog errors have been resolved [mentioned in 
another post].


I answered many of the questions you are asking in thew original 
email, but I will try to answer once again.


 You ask (see at this point HTML is easier to show the difference 
between your questions and my answers) :
When you start Evolution (without importing the backup file) what 
issues do you have?

I answer: I never used evolution on the desktop before the import of 
the gz file and now, even after allegedly purging the problem exists 
after a 'clean' install. But I can't be sure it is truly clean.

You ask: The version of Evolution you're using (not the version of the 
distribution or desktop).  You can use Help -> About to find  this.

Answered two days ago: 3.38.3-1


You ask: The type of email server you are using (IMAP, POP, EWS, etc.) 
and       any special/non-default settings you use with it.

Answered three days ago: POP

You ask:  A concise explanation of the problem you are having.
Answered three days ago: And no it isn't possible to be concise 
without you complaining later that I left out significant parts. But 
here is the very short form. I'm sure I will regret this.
(A) There are two instances of evolution: #1 on a Debian VM and one on 
that same PC desktop running the same version of Debian.
(B) The VM was used to import all my Outlook PST files (there were 
five PSTs). That VM still exists and, when run with that instance of 
evolution running, that evolution works fine. I exported the data from 
that instance. I then sFTPed the gz file to (C) below.

(C) The desktop install of the same version of evolution was done with 
the importing of the gz file. I never used the software prior to the 
import.
(D) for a few hours the desktop version ran OK and then it stopped 
displaying any incoming mail. If I used it to she mail, the mail would 
be sent, but it didn't appear in the sent folder or anywhere else.

(Also) as I am using Debian, I use the apt-get for that version that 
is maintained by that maintainer. That is the *current version* on 
Debian. *So it DOES matter what platform I am on.* Are you saying I 
should use a different version from a different source?


Yours,
Mike Lieberman
Imagine whirled peas


On Monday 11/07/2022 at 02:06, Paul Smith  wrote:
>>
>> On Sun, 2022-11-06 at 06:07 +0000, Mike wrote:
>>>
>>>
>>> I purged evolution from the PC, deleted the .config/evolution
>>> folders, deleted the trash, rebooted, reinstalled at 12:36 and ran it
>>> at 12:37. I did not import the backup file, so that isn't the
>>> problem.
>>>
>>> None of these errors are in the VM install though the VM install
>>> happened only five days ago, both via ftp.debian.org via apt-get onto
>>> the same computer (one instance the VirtualBox Debian 11.5 and the
>>> other on the actual hardware running Debian 11.5)
>>>
>>> Without importing the backup, I see this:
>>
>> Hi Mike. All of these log messages are just warnings about the
>> codebase, which should be fixed but don't have any direct impact on  
>> the
>> application (most likely) [1].
>>
>> Although there are lots of scary messages here it APPEARS that
>> everything came up successfully. Above you say "that isn't the
>> problem", but you didn't describe what the problem is.
>>
>> When you start Evolution (without importing the backup file) what
>> issues do you have?
>>
>> The important information we must have to start thinking about a
>> problem is:
>>
>> * The version of Evolution you're using (not the version of the
>>            distribution or desktop).  You can use Help -> About to 
>> find  this.
>> * The type of email server you are using (IMAP, POP, EWS, etc.) and
>>            any special/non-default settings you use with it.
>> * A concise explanation of the problem you are having.
>>
>> All the rest of the details, such as which desktop you're using, what
>> was imported, etc. are almost certainly not relevant (unless the
>> problem is related to a failure to import etc.) It's fine to include
>> them but please format your question so that the most relevant details
>> are clearly stated up at the top, so we don't have to spelunk a long
>> email of other details to dig them out.
>>
>> Also helpful is to use a subject line that encapsulates the problem
>> you're having in a short sentence, rather than one that doesn't help  
>> us
>> find this issue in archives etc.
>>
>> And finally, it's helpful to us as readers if you avoid complex/fancy
>> HTML signatures, etc. and stick with just plain text as much as
>> possible. And we do appreciate if you can trim your replies to contain
>> only the specific text you're replying to, and not include the entire
>> email thread in your reply. We have mailing list archives for anyone
>> who wants to see the history, and including replies makes those more
>> difficult to read. Evolution makes this easy: just select (with your
>> mouse) the text you want to reply to and then hit the reply button,  
>> and
>> only that text will be quoted in the reply.
>>
>> I feel like we got off on lots of probably-not-relevant tangents such
>> as whether it's better to use a local IMAP server, etc. These are
>> interesting topics but I doubt very much they're related to the issues
>> you're seeing.
>>
>> Perhaps it's best to start a new thread with the details needed to
>> address one specific problem you are having and see if we can solve  
>> it.
>>
>> Hopefully we can help!!
>>
>>
>> [1] Just to note, you are using (if I recall correctly) a pretty old
>> version of Evolution. The current version is 3.46. You are using 3.38
>> which is 4 releases ago. It's not going to be the case that these  
>> types
>> of warnings will ever be addressed in that old version.
>
>
>



_______________________________________________
evolution-list mailing list
[email protected]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list