Re: [Evolution] Error fetching message info: unknown body response
On Tue, 2018-10-23 at 10:54 -0400, Josh wrote: > I believe I did exactly like you said, CAMEL_DEBUG=all Hi, I'm sorry, but you didn't. The CAMEL_DEBUG=all is useless, it contains too much information. I wanted you to use a specific logging, more targeted to the issue you have. > and only one folder in the log. Okay, good, but it doesn't contain the response from the server, it's cut at the place where the error message is logged with not enough lines above it. Bye, 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
Re: [Evolution] Error fetching message info: unknown body response
On 10/23/18 03:13, Milan Crha via evolution-list wrote: On Mon, 2018-10-22 at 18:47 -0400, Josh wrote: [imapx:A] camel_imapx_server_process_command_sync: 0x7f469c00e300 ~> (nil); success:0 local-error:unknown body response result:[null] status-text:'[null]' [imapx:A] Removed connection 0x7f46ec087c90 (server:0x55e507ff9d80) due to error: Error fetching message info: unknown body response [imapx:A] I/O: '' ... Evolution 3.28.5 (3.28.5-1.fc28) Anything else I can provide to help diagnosing the problem? Hi, it's odd to see such error with 3.28.5 (I suppose your evolution-data- server is also 3.28.5, the one provided by Fedora repositories). These errors used to be due to unexpected (or incorrect) BODYSTRUCTURE responses from the server, but 3.28.5 doesn't ask for it, it had been in 3.30.0+ only. There had been done several fixes to address BODYSTRUCTURE issues gracefully, all are part of 3.30.2 release (of evolution-data-server). Why you see it I do not know. For the debugging, you skipped the most important part. You might have enabled only one IMAP account, if you've more, to avoid log messages interleaving. Run evolution from a terminal like this: $ CAMEL_DEBUG=imapx:io,imapx:conman evolution then select the folder with the issue, observe the error and close evolution. Find the error in the log and the lines above it are important. How many lines I cannot tell you, it depends on many things (like how many messages are going to be downloaded, how many headers each have, and such). Possibly the closes "UID FETCH 123:456 (RFC822.SIZE RFC822.HEADER FLAGS)" before the error is the one which runs the request. Then there are responses to it, where one of them is causing the error. It's not necessarily the last one, because the data is read from the server in chunks. I believe I did exactly like you said, CAMEL_DEBUG=all and only one folder in the log. Above lines I provided is a full header of last message downloaded. Josh. ___ 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] Messages sorting in message list
Il giorno sab, 20/10/2018 alle 18.57 +0100, Pete Biggs ha scritto: > > Of course I know how it works basically. But this applies the sorting > > also to messages *inside* the thread. I don't want it so. I want to get > > messages of a thread ordered by date/ascending, since there could be > > replies to oders branches of a thread that come first (and It's simpler > > for reading to have them displayed on top). > > > As far as I can see in my version (3.28.5) if you sort by date > descending (i.e. most recent at top) the threads are sorted internally > by date ascending (i.e. most recent at bottom). Is that not what you > want? > Yes, it is, but it doesn't seem to follow that logic. I'll show you a thread of this ML as an example. 1. https://postimg.cc/Jt4JDY2h 2. https://postimg.cc/z3thnwsF pic n.1 is thunderbird; pic n.2 is evolution. Both are message list with date/discending ordering. msg.1 e msg.2 are at the same "level"... n.1 shows thread's messages in ascending mode... so msg.1 come before (on top) since its date is previous than msg.2. n.2 show the opposite: also msgs are ordered by date/discending; msg.2 come before (on top)... this makes more difficult to follow the "thread of thought" imo, than the case n.1. In thunderbird, thread internal ordering of messages does not change if I change the "global" ordering (as i.e. I select ordering ascending or descending by date, internally it's always ascending); in evolution it does. -- fp ___ 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] Command to "Send as attachment"
On Mon, 2018-10-22 at 18:01 +0200, Ralf Mardorf via evolution-list wrote: > On Mon, 2018-10-22 at 16:24 +0100, Patrick O'Callaghan wrote: > > On Mon, 2018-10-22 at 10:54 +0200, Ralf Mardorf via evolution-list > > wrote: > > > PS: > > > > > > To sent mails by command line I wouldn't use Evolution with 'mailto'. > > > Consider to use a 'sendmail' replacement such as 'msmtp', see > > > https://mail.gnome.org/archives/evolution-list/2014-May/msg00183.html. > > > > SendEmail is another option. 'dnf install sendemail'. > > Hi, > > while it seems to be easy to use, upstream unfortunately released the > last version 9 years ago. > > On Arch Linux: $ yaourt -Syua sendemail > > http://caspian.dotconf.net/menu/Software/SendEmail/ > https://tecadmin.net/send-email-from-gmail-smtp-via-linux-command/ There is a Fedora package for F28 (latest stable version) so I don't think that matters. SMTP hasn't changed in 9 years. 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] Error fetching message info: unknown body response
On Mon, 2018-10-22 at 18:47 -0400, Josh wrote: > [imapx:A] camel_imapx_server_process_command_sync: 0x7f469c00e300 ~> > (nil); success:0 local-error:unknown body response result:[null] > status-text:'[null]' > [imapx:A] Removed connection 0x7f46ec087c90 (server:0x55e507ff9d80) > due > to error: Error fetching message info: unknown body response > [imapx:A] I/O: '' > ... > > > Evolution 3.28.5 (3.28.5-1.fc28) Anything else I can provide to help > diagnosing the problem? Hi, it's odd to see such error with 3.28.5 (I suppose your evolution-data- server is also 3.28.5, the one provided by Fedora repositories). These errors used to be due to unexpected (or incorrect) BODYSTRUCTURE responses from the server, but 3.28.5 doesn't ask for it, it had been in 3.30.0+ only. There had been done several fixes to address BODYSTRUCTURE issues gracefully, all are part of 3.30.2 release (of evolution-data-server). Why you see it I do not know. For the debugging, you skipped the most important part. You might have enabled only one IMAP account, if you've more, to avoid log messages interleaving. Run evolution from a terminal like this: $ CAMEL_DEBUG=imapx:io,imapx:conman evolution then select the folder with the issue, observe the error and close evolution. Find the error in the log and the lines above it are important. How many lines I cannot tell you, it depends on many things (like how many messages are going to be downloaded, how many headers each have, and such). Possibly the closes "UID FETCH 123:456 (RFC822.SIZE RFC822.HEADER FLAGS)" before the error is the one which runs the request. Then there are responses to it, where one of them is causing the error. It's not necessarily the last one, because the data is read from the server in chunks. Bye, 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
