Re: [Evolution] exhange offline message storage: questions and troubleshooting
On Sat, 2012-12-15 at 18:50 +0100, Adam Gold wrote: Hi there. I've just installed evolution and evolution-ews and have successfully connected to my exchange server. Hi, what is the evolution/evolution-ews version, please? You can, in Evolution, Help-About to find it. I'm having problems downloading my messages from the server so I wanted to clarify about how the offline mail storage works. Does it tell you any error, either in UI, or if you run evolution on a console? - In Evolution in preferences -- mail accounts -- edit-- receving options there is check box for automatically synchronize remote mail locally. I have two questions about this: (i) does this mean all messages received to this exchange account post installation and selection of this option will be cached locally; Correct. (ii) does this initiate a full download of all historical messages It's usually used for newly discovered messages (not necessarily new), not for old one. - I see that one can also right-click on a particular folder's preferences and there is an option copy folder content locally for offline operation. Is this the same as the previous option but simply on a folder by folder basis? Correct. Sometimes you do not want to download locally your Archive folder, then this is for it. Even if I try one or both of these options, I can't seem to download all of my stored messages from the server. The download begins and then stops after which I have to manually start it again. Also periodically I get a warning notice that messages can't be moved from the cache. What is the exact warning, please? Is there anything on console? You can see what evolution-ews does and your server responses, if you run evolution like this: $ EWS_DEBUG=2 evolution This seems to be confirmed when I look in ~/.cache and compare it to the contents of .local/share/evolution/mail/local. The latter is near empty and the former has appx 100mb. Evolution-ews stores its data into ~/.cache/..., while your local mail, those in On This Computer/... are in ~/.local/ You might not cope with these folders at all, those are internal evolution/-ews folders and files. Hope it helps, Milan ___ 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] English GUI
Hi, I searched the archive for I remember someone wrote here how to start ONE TIME with the English GUI. I think it was a command line with LANG=EN in it, but it was little more ? Sorry, can't find it. I'm I wrong and it was another list ? Or is - as usual - the search parameter not the right one ? -- Best, Thomas ___ 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] English GUI
Le lundi 17 décembre 2012 à 14:28 +0100, Thomas Prost a écrit : Hi, I searched the archive for I remember someone wrote here how to start ONE TIME with the English GUI. I think it was a command line with LANG=EN in it, but it was little more ? Sorry, can't find it. I'm I wrong and it was another list ? Or is - as usual - the search parameter not the right one ? Hello, LC_ALL=en evolution should work. Regards, -- Bastien Durel ___ 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] bus error causing crashes
On Sat, 2012-12-15 at 07:11 +, Pete Biggs wrote: using Debian Sid/unstable with Evolution 3.4.4 (but happened since 3.4.x), wanting to reply to some message, Evolution often crashes due to a »bus error«. Does somebody experience something similar? I think that is a euphamism for a segmentation fault. No, they are different things - a seg fault is when a program attempts to access a memory segment it doesn't own and a bus error is when a program attempts to access memory beyond the capabilities of the machine. Both are caused by similar things, such as dereferencing invalid pointers, but bus errors sometimes point to hardware problems. A common error resulting in SIGBUS is accessing a memory mapped file beyond the end of the file but still inside the memory map. A program of mine often gets this signal (when I have a bug) because I mmap a full 1 GB in order to reserve that virtual memory for an expanding file, but the file may be only 550 MB. The mmap man page documents that. -- Knowledge Is Power Power Corrupts Study Hard Be Evil signature.asc Description: This is a digitally signed message part ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
