Re: [Evolution] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]

[Svante Signell <svante signell telia com>]

On Tue, 2012-10-30 at 12:33 +0000, Pete Biggs wrote:
 
> And the "strange name" is actually the UID of the account within Evo,
> which you will be able to see at the beginning of the line from gconf.

OK!

> > > Have you actually looked to see if the actual spool file is accessed at
> > > all?  
> >
> > How to know if evo tries to accesses it? logcheck is reporting there so
> > this spool file is updated often.
>
> inotifywatch will tell you when a file is accessed (by anything).
>
>     strace -f -e trace=file evolution

I see the following with strace:

/home/<user>/.local/share/evolution/mail/spool/: (No such file or directory)
/home/<user>/.local/share/evolution/mail/smtp/<user isp>:465 (No such file or directory)
 stat64("/var/mail/<user>" etc = 0
 open("/var/mail/<user>", O_RDONLY|O_LARGEFILE) = 33

Several times: (varying 6 char extension to <user>. 
stat64("/var/mail/<user>", {st_mode=S_IFREG|0660, st_size=95669778, ...}) = 0
open("/var/mail/<user>RKL7MW", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0600) = -1 EACCES (Permission denied)

(evolution:16230): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memor
y.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Could not lock '/var/mail/<user>'
(evolution:16230): evolution-mail-WARNING **: Failed to refresh folders: Summary and folder mismatch, even 
after a sync

(evolution:16230): camel-WARNING **: Could not lock '/var/mail/s<user>'

(evolution:16230): camel-WARNING **: CamelVTrashFolder::synchronize_sync() set its GError but then reported 
success

(evolution:16230): camel-WARNING **: Error message was: Error storing 'mailbox: /<usr>/INBOX (spool)': Could 
not lock '/var/mail/<user>'

(evolution:16230): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Operation was cancelled

(evolution:16230): evolution-mail-WARNING **: Failed to refresh folders: Error storing 'mailbox: 
/<user>/INBOX (spool)': Could not lock '/var/mail/<user>'

(And so on ...)


> > Evo is reporting several thousands of mails available  but cannot find
> > the mails themselves.
>
> Is there actually that many messages in the spool file?

2900 messages, yes!

> > > > > <url>spool:/var/mail/username</url> - do you see that?
> > > >
> > > > Yes I see it now: <url>spool:///var/mail/"username"</url>
> > > > It seem to be correct, why does not evo find it?

> Does the config within Evolution have three slashes?  Can you change it
> there?

No it has /var/mail/<user>
 
> If you need to play with the gconf entries, use gconf-editor


I changed to two slashes and one slash, same or worse problem.