Re: [Evolution] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]
> ping! My upstream mail provider was bouncing messages ... > On Sat, 2012-12-08 at 13:47 +0100, Svante Signell wrote: > > On Fri, 2012-11-30 at 00:20 +, Pete Biggs wrote: > > > > > > > > > Have you run Evolution with debugging enabled on this newly installed > > > > > computer? Does it show any errors or problems? > > > > > > > > Not yet, will try that. > > > > The only debug flag from the man page says: > >--debug=FILE > > Send the debugging output of all components to FILE. > > > > Is that how debugging is enabled? What about verbosity levels? No, that's not how to enable debugging. The information you need is on the page at http://projects.gnome.org/evolution/bugs.shtml Basically you start evolution using the command line CAMEL_DEBUG=all evolution > > > > Attached is a heavily edited diff of strace (diff -u imap.out imap > > +local.out) for a imap account enabled, and imap+local spool enabled. > > Nothing immediate I can see here, maybe you do. Perhaps I removed too > > much information by mistake, but the log files were 12Mb+ large. > > I don't think the strace is much use in this form - the diff takes out all information on what the file handles refer to. Try the debug options first. P. ___ 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] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]
ping! On Sat, 2012-12-08 at 13:47 +0100, Svante Signell wrote: > On Fri, 2012-11-30 at 00:20 +, Pete Biggs wrote: > > > > > > > Have you run Evolution with debugging enabled on this newly installed > > > > computer? Does it show any errors or problems? > > > > > > Not yet, will try that. > > The only debug flag from the man page says: >--debug=FILE > Send the debugging output of all components to FILE. > > Is that how debugging is enabled? What about verbosity levels? > > Attached is a heavily edited diff of strace (diff -u imap.out imap > +local.out) for a imap account enabled, and imap+local spool enabled. > Nothing immediate I can see here, maybe you do. Perhaps I removed too > much information by mistake, but the log files were 12Mb+ large. > ___ 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] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]
On Fri, 2012-11-30 at 00:20 +, Pete Biggs wrote:
> >
> > > Have you run Evolution with debugging enabled on this newly installed
> > > computer? Does it show any errors or problems?
> >
> > Not yet, will try that.
The only debug flag from the man page says:
--debug=FILE
Send the debugging output of all components to FILE.
Is that how debugging is enabled? What about verbosity levels?
Attached is a heavily edited diff of strace (diff -u imap.out imap
+local.out) for a imap account enabled, and imap+local spool enabled.
Nothing immediate I can see here, maybe you do. Perhaps I removed too
much information by mistake, but the log files were 12Mb+ large.
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=12, events=POLLIN}, {fd=7, events=POLLIN}], 5, 0) = 0 (Timeout)
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
-writev(3, [{"5\30\4\0\346\1 \3\"\0 \3g\1\34\0\224\4\6\0\347\1 \3\346\1 \3*\0\0\0"..., 2792}, {NULL, 0}, {"", 0}], 3) = 2792
-recvfrom(3, 0x7f29fc9c1ad4, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
-recvfrom(3, 0x7f29fc9c1ad4, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
-poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=12, events=POLLIN}, {fd=7, events=POLLIN}], 5, 29) = 0 (Timeout)
-recvfrom(3, 0x7f29fc9c1ad4, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
+writev(3, [{"5\30\4\0\362\1 \3\"\0 \3\317\2\34\0\224\4\6\0\363\1 \3\362\1 \3*\0\0\0"..., 4088}, {NULL, 0}, {"", 0}], 3) = 4088
+recvfrom(3, 0x7f1795d65ad4, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
+recvfrom(3, 0x7f1795d65ad4, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
+poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=12, events=POLLIN}, {fd=7, events=POLLIN}], 5, 32
+(evolution:5302): camel-local-prrecvfrom(3, 0x7f1795d65ad4, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
+
+(evolution:5302): evolution-mail-WARNING **: Failed to refresh folders: Summary and folder mismatch, even after a sync
+poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=12, events=POLLIN}, {fd=7, events=POLLIN}], 5, 0) = 1 ([{fd=4, revents=POLLIN}])
+read(4, "\4\0\0\0\0\0\0\0", 16) = 8
+recvfrom(3, 0x7f1795d65ad4, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=12, events=POLLIN}, {fd=7, events=POLLIN}], 5, 0) = 0 (Timeout)
+read(4, 0x7fff7890a350, 16) = -1 EAGAIN (Resource temporarily unavailable)
+lstat("/usr/share/icons/gnome/22x22/status/mail-unread.png", {st_mode=S_IFREG|0644, st_size=1100, ...}) = 0
+lstat("/usr/share/icons/gnome/16x16/status/mail-unread.png", {st_mode=S_IFREG|0644, st_size=773, ...}) = 0
+
+(evolution:5302): camel-local-provider-WARNING **: Didn't get the next message where I expected (90262) got 0 instead
+{st_mode=S_IFREG|0644, st_size=1254, ...}) = 0
+lstat("/usr/share/icons/gnome/32x32/status/mail-unread.png",
+(evolution:5302): camel-WARNING **: Summary and folder mismatch, even after a sync
+{st_mode=S_IFREG|0644, st_size=1687, ...}) = 0
+
+(evolution:5302): camel-WARNING **: CamelVTrashFolder::synchronize_sync() set its GError but then reported success
+
+(evolution:5302): camel-WARNING **: Error message was: Error storing 'mailbox: /user/INBOX (spool)': Summary and folder mismatch, even after a sync
+
+(evolution:5302): camel-WARNING **: CamelVTrashFolder::refresh_info_sync() set its GError but then reported success
+
+(evolution:5302): camel-WARNING **: Error message was: Error storing 'mailbox: /user/INBOX (spool)': Summary and folder mismatch, even after a sync
+
+(evolution:5302): evolution-mail-WARNING **: Failed to refresh folders: Error storing 'mailbox: /user/INBOX (spool)': Summary and folder mismatch, even after a sync
+lstat("/usr/share/icons/gnome/48x48/status/mail-unread.png", {st_mode=S_IFREG|0644, st_size=2609, ...}) = 0
+poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
+writev(3, [{"\22\0004\22\"\0 \3?\1\0\0\6\0\0\0 \4\6\0.\22\0\0\26\0\0\0\26\0\0\0"..., 16384}, {NULL, 0}, {"", 0}], 3) = 16384
+recvfrom(3, 0x7f1795d65ad4, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
+
+(evolution:5302): camel-WARNING **: Summary and folder mismatch, even after a sync
+
+(evolution:5302): camel-WARNING **: CamelVTrashFolder::synchronize_sync() set its GError but then reported success
+
+(evolution:5302): camel-WARNING **: Error message was: Error storing 'mailbox: /user/INBOX (spool)': Summary and folder mismatch, even after a sync
+
+(evolution:5302): camel-WARNING **: CamelVTrashFolder::refresh_info_sync() set its GError but then reported success
+
+(evolution:5302): camel-WARNING **: Error message was: Error storing 'mailbox: /user/INBOX (spool)': Summary and folder mismatch, even after a sync
+
+(evolut
Re: [Evolution] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]
> > > Have you run Evolution with debugging enabled on this newly installed > > computer? Does it show any errors or problems? > > Not yet, will try that. > BTW: does the user have to be part of the mail group? > >From the point of view of Evolution, no the user doesn't have to be a member of the mail group so long as the mail spool file in /var/mail/ is owned by the user. P. ___ 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] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]
On Thu, 2012-11-29 at 22:38 +, Pete Biggs wrote: > On Thu, 2012-11-29 at 23:19 +0100, Svante Signell wrote: > > On Wed, 2012-11-28 at 19:07 +0100, Svante Signell wrote: > > > On Wed, 2012-10-31 at 16:14 +0100, Svante Signell wrote: > > > > On Wed, 2012-10-31 at 13:45 +, Pete Biggs wrote: > > > > > > > > > OK. I've done some more Googling on your behalf - there was a > > > > > Debian/Ubuntu packaging bug that might affect you - basically make > > > > > sure > > > > > that /usr/lib/evolution/camel-lock-helper-1.2 is SGID mail. > > > > > > > > Thanks for your help so far. Still not the problem cause: > > > > ls -l /usr/lib/evolution/camel-lock-helper-1.2 > > > > -rwxr-sr-x 1 root mail 13720 Oct 22 > > > > 16:00 /usr/lib/evolution/camel-lock-helper-1.2 > > > > > > Hi, I have now created a local mbox account on a newly installed > > > computer, and the same problem exists there. How to go forward from here > > > with debugging? > > > > Please, any ideas? Regarding the patch mentioned in bug #640851 > > it _is_ applied for 3.4.4. Something else is causing problems. > > > > Have you copied over your user files to this newly installed computer? Nope! > Did you ever create a new Unix account and try the same thing from that? You mean on the old computer or the new one? On the new one, the account is created from scratch. > Have you run Evolution with debugging enabled on this newly installed > computer? Does it show any errors or problems? Not yet, will try that. BTW: does the user have to be part of the mail group? Thanks! ___ 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] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]
On Thu, 2012-11-29 at 23:19 +0100, Svante Signell wrote: > On Wed, 2012-11-28 at 19:07 +0100, Svante Signell wrote: > > On Wed, 2012-10-31 at 16:14 +0100, Svante Signell wrote: > > > On Wed, 2012-10-31 at 13:45 +, Pete Biggs wrote: > > > > > > > OK. I've done some more Googling on your behalf - there was a > > > > Debian/Ubuntu packaging bug that might affect you - basically make sure > > > > that /usr/lib/evolution/camel-lock-helper-1.2 is SGID mail. > > > > > > Thanks for your help so far. Still not the problem cause: > > > ls -l /usr/lib/evolution/camel-lock-helper-1.2 > > > -rwxr-sr-x 1 root mail 13720 Oct 22 > > > 16:00 /usr/lib/evolution/camel-lock-helper-1.2 > > > > Hi, I have now created a local mbox account on a newly installed > > computer, and the same problem exists there. How to go forward from here > > with debugging? > > Please, any ideas? Regarding the patch mentioned in bug #640851 > it _is_ applied for 3.4.4. Something else is causing problems. > Have you copied over your user files to this newly installed computer? Did you ever create a new Unix account and try the same thing from that? Have you run Evolution with debugging enabled on this newly installed computer? Does it show any errors or problems? P. ___ 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] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]
On Wed, 2012-11-28 at 19:07 +0100, Svante Signell wrote: > On Wed, 2012-10-31 at 16:14 +0100, Svante Signell wrote: > > On Wed, 2012-10-31 at 13:45 +, Pete Biggs wrote: > > > > > OK. I've done some more Googling on your behalf - there was a > > > Debian/Ubuntu packaging bug that might affect you - basically make sure > > > that /usr/lib/evolution/camel-lock-helper-1.2 is SGID mail. > > > > Thanks for your help so far. Still not the problem cause: > > ls -l /usr/lib/evolution/camel-lock-helper-1.2 > > -rwxr-sr-x 1 root mail 13720 Oct 22 > > 16:00 /usr/lib/evolution/camel-lock-helper-1.2 > > Hi, I have now created a local mbox account on a newly installed > computer, and the same problem exists there. How to go forward from here > with debugging? Please, any ideas? Regarding the patch mentioned in bug #640851 it _is_ applied for 3.4.4. Something else is causing problems. ___ 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] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]
On Wed, 2012-10-31 at 16:14 +0100, Svante Signell wrote: > On Wed, 2012-10-31 at 13:45 +, Pete Biggs wrote: > > > OK. I've done some more Googling on your behalf - there was a > > Debian/Ubuntu packaging bug that might affect you - basically make sure > > that /usr/lib/evolution/camel-lock-helper-1.2 is SGID mail. > > Thanks for your help so far. Still not the problem cause: > ls -l /usr/lib/evolution/camel-lock-helper-1.2 > -rwxr-sr-x 1 root mail 13720 Oct 22 > 16:00 /usr/lib/evolution/camel-lock-helper-1.2 Hi, I have now created a local mbox account on a newly installed computer, and the same problem exists there. How to go forward from here with debugging? ___ 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] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]
Hi,
On Tue, Oct 30, 2012 at 10:44:47PM +, Pete Biggs wrote:
> > I see the following with strace:
> >
> > /home//.local/share/evolution/mail/spool/: (No such file or directory)
> > /home//.local/share/evolution/mail/smtp/:465 (No such file
> > or directory)
> > stat64("/var/mail/" etc = 0
> > open("/var/mail/", O_RDONLY|O_LARGEFILE) = 33
> >
> > Several times: (varying 6 char extension to .
> > stat64("/var/mail/", {st_mode=S_IFREG|0660, st_size=95669778, ...}) = > > 0
> > open("/var/mail/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/'
>
> And that is the root of all your problems.
AFAICT, camel-lock-helper won't work if you run it under strace, likely
because the setgid privs are being stripped and then it does not have
the permissions to create a lockfile in /var/mail (it just confused my
for a while when I tried to reproduce the problem).
So the above is probably bogus.
Michael
___
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] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]
On Wed, 2012-10-31 at 13:45 +, Pete Biggs wrote: > OK. I've done some more Googling on your behalf - there was a > Debian/Ubuntu packaging bug that might affect you - basically make sure > that /usr/lib/evolution/camel-lock-helper-1.2 is SGID mail. Thanks for your help so far. Still not the problem cause: ls -l /usr/lib/evolution/camel-lock-helper-1.2 -rwxr-sr-x 1 root mail 13720 Oct 22 16:00 /usr/lib/evolution/camel-lock-helper-1.2 ___ 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] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]
> > > > OK. But the bottom line is that Evolution can't get a lock on your mail > > spool file - if it can't get a lock, then it can't do anything with it. > > If the permissions on the file are correct, then there must be some > > other process holding a lock on it. You need to find out which process > > that is and why it is holding a lock. > > > > Processes having locks are: > 32629 2.8 10.6 536428 165880 ? Sl 09:12 > 2:36 /usr/lib/iceweasel/firefox-bin > 1978 0.0 0.0 212812 ? Ss Oct10 0:00 /usr/sbin/atd > daemon1574 0.0 0.0 1960 304 ? Ss Oct10 0:00 /sbin/portmap > > and a non-existing process with PID 2105: > 7: FLOCK ADVISORY WRITE 2105 00:0e:7109 0 EOF > What does this mean?? > > None of them are listing the inode number I have for /var/mail/ > ls -li /var/mail/ > 15811 -rw-rw 1 mail 95736997 Oct 31 10:02 /var/mail/ > OK. I've done some more Googling on your behalf - there was a Debian/Ubuntu packaging bug that might affect you - basically make sure that /usr/lib/evolution/camel-lock-helper-1.2 is SGID mail. P. ___ 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] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]
On Tue, 2012-10-30 at 12:33 +, 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//.local/share/evolution/mail/spool/: (No such file or directory)
/home//.local/share/evolution/mail/smtp/:465 (No such file or
directory)
stat64("/var/mail/" etc = 0
open("/var/mail/", O_RDONLY|O_LARGEFILE) = 33
Several times: (varying 6 char extension to .
stat64("/var/mail/", {st_mode=S_IFREG|0660, st_size=95669778, ...}) = 0
open("/var/mail/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/'
(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'
(evolution:16230): camel-WARNING **: CamelVTrashFolder::synchronize_sync() set
its GError but then reported success
(evolution:16230): camel-WARNING **: Error message was: Error storing 'mailbox:
//INBOX (spool)': Could not lock '/var/mail/'
(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: //INBOX (spool)': Could not lock '/var/mail/'
(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!
> > > > > spool:/var/mail/username - do you see that?
> > > >
> > > > Yes I see it now: spool:///var/mail/"username"
> > > > 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/
> If you need to play with the gconf entries, use gconf-editor
I changed to two slashes and one slash, same or worse problem.
___
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] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]
On Wed, 2012-10-31 at 09:37 +, Pete Biggs wrote: > > > > > > 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/' > > > > > > And that is the root of all your problems. > > > > > > Check the ownership and permissions on the /var/mail/ file - it > > > should be owned by . group should be "mail", and permissions > > > should be -rw-rw (i.e. rw by user and group, no world permissions). > > > > They are: > > -rw-rw 1 mail 95684923 Oct 31 07:02 /var/mail/ > > > > and ls -ld /var/mail shows: > > drwxrwsr-x 2 root mail 4096 Oct 31 07:21 /var/mail/ > > > > and is in the group mail. > > OK. But the bottom line is that Evolution can't get a lock on your mail > spool file - if it can't get a lock, then it can't do anything with it. > If the permissions on the file are correct, then there must be some > other process holding a lock on it. You need to find out which process > that is and why it is holding a lock. > > To save you asking, use the lslk utility to list the current locks on > files. If you can't find lslk (it's an old and unmaintained utility), > look in /proc/locks - the information in there is not user friendly, but > it contains lines such as: > > 1: POSIX ADVISORY WRITE 4953 08:11:17703846 1073741824 1073742335 > ^ ^ >PID inode number > > So you need to find the inode number of your mail spool file and see if > it's listed. Processes having locks are: 32629 2.8 10.6 536428 165880 ? Sl 09:12 2:36 /usr/lib/iceweasel/firefox-bin 1978 0.0 0.0 212812 ? Ss Oct10 0:00 /usr/sbin/atd daemon1574 0.0 0.0 1960 304 ? Ss Oct10 0:00 /sbin/portmap and a non-existing process with PID 2105: 7: FLOCK ADVISORY WRITE 2105 00:0e:7109 0 EOF What does this mean?? None of them are listing the inode number I have for /var/mail/ ls -li /var/mail/ 15811 -rw-rw 1 mail 95736997 Oct 31 10:02 /var/mail/ ___ 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] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]
>
> > > 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/'
> >
> > And that is the root of all your problems.
> >
> > Check the ownership and permissions on the /var/mail/ file - it
> > should be owned by . group should be "mail", and permissions
> > should be -rw-rw (i.e. rw by user and group, no world permissions).
>
> They are:
> -rw-rw 1 mail 95684923 Oct 31 07:02 /var/mail/
>
> and ls -ld /var/mail shows:
> drwxrwsr-x 2 root mail 4096 Oct 31 07:21 /var/mail/
>
> and is in the group mail.
OK. But the bottom line is that Evolution can't get a lock on your mail
spool file - if it can't get a lock, then it can't do anything with it.
If the permissions on the file are correct, then there must be some
other process holding a lock on it. You need to find out which process
that is and why it is holding a lock.
To save you asking, use the lslk utility to list the current locks on
files. If you can't find lslk (it's an old and unmaintained utility),
look in /proc/locks - the information in there is not user friendly, but
it contains lines such as:
1: POSIX ADVISORY WRITE 4953 08:11:17703846 1073741824 1073742335
^ ^
PID inode number
So you need to find the inode number of your mail spool file and see if
it's listed.
>
> I believe the UID has been the same for a long time. The problems
> started in end of June, probably with the upgrade from evo 3.4.2 to
> 3.4.3.
This NOT an Evolution problem. Evolution is doing the correct thing -
or at least the system is doing the correct thing by not allowing
Evolution access to a file that another process has a lock on.
>
> More strace output:
> [pid 16240] open("/var/mail/", O_RDWR|O_LARGEFILE) = 33
> [pid 16240] open("/tmp/spool.camel.7JY6MW", O_RDWR|O_CREAT|O_EXCL|
> O_LARGEFILE, 0600) = 35
>
> (evolution:16230): camel-local-provider-WARNING **: Didn't get the next
> message where I expected (543185) got 0 instead
> [pid 16240] unlink("/tmp/spool.camel.7JY6MW") = 0
>
> (evolution:16230): camel-WARNING **: CamelSpoolStore::get_folder_sync()
> set its GError but then reported success
>
> (evolution:16230): camel-WARNING **: Error message was: Summary and
> folder mismatch, even after a sync
>
Some of these may be small bugs in Evo, but they are bugs that are only
being triggered by the underlying issue that Evo can not successfully
access the mail spool file, they are not bugs that are causing the
problem. The "Summary and folder mismatch" error is probably being
caused by the fact that Evo updates the summary information in its local
store, then can't actually update the mail folder (i.e. spool file) to
match what has been summarised, and the next time it tries to do things
with the mail folder it gets confused.
P.
___
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] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]
On Tue, 2012-10-30 at 22:44 +, Pete Biggs wrote:
> >
> > I see the following with strace:
> >
> > 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/'
>
> And that is the root of all your problems.
>
> Check the ownership and permissions on the /var/mail/ file - it
> should be owned by . group should be "mail", and permissions
> should be -rw-rw (i.e. rw by user and group, no world permissions).
They are:
-rw-rw 1 mail 95684923 Oct 31 07:02 /var/mail/
and ls -ld /var/mail shows:
drwxrwsr-x 2 root mail 4096 Oct 31 07:21 /var/mail/
and is in the group mail.
> I suspect that at some point you have upgraded or changed your distro
> and although you have used the same username, the UID of that user has
> changed - hence the mail spool file is called the correct thing, but is
> not owned by the correct user.
I believe the UID has been the same for a long time. The problems
started in end of June, probably with the upgrade from evo 3.4.2 to
3.4.3.
More strace output:
[pid 16240] open("/var/mail/", O_RDWR|O_LARGEFILE) = 33
[pid 16240] open("/tmp/spool.camel.7JY6MW", O_RDWR|O_CREAT|O_EXCL|
O_LARGEFILE, 0600) = 35
(evolution:16230): camel-local-provider-WARNING **: Didn't get the next
message where I expected (543185) got 0 instead
[pid 16240] unlink("/tmp/spool.camel.7JY6MW") = 0
(evolution:16230): camel-WARNING **: CamelSpoolStore::get_folder_sync()
set its GError but then reported success
(evolution:16230): camel-WARNING **: Error message was: Summary and
folder mismatch, even after a sync
[pid 16240]
access("/home//.local/share/evolution/mail//folders.db-journal",
F_OK) = -1 ENOENT (No such file or directory)
[pid 16240]
access("/home//.local/share/evolution/mail//folders.db-wal",
F_OK) = -1 ENOENT (No such file or directory)
___
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] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]
>
> I see the following with strace:
>
> /home//.local/share/evolution/mail/spool/: (No such file or directory)
> /home//.local/share/evolution/mail/smtp/:465 (No such file or
> directory)
> stat64("/var/mail/" etc = 0
> open("/var/mail/", O_RDONLY|O_LARGEFILE) = 33
>
> Several times: (varying 6 char extension to .
> stat64("/var/mail/", {st_mode=S_IFREG|0660, st_size=95669778, ...}) = 0
> open("/var/mail/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/'
And that is the root of all your problems.
Check the ownership and permissions on the /var/mail/ file - it
should be owned by . group should be "mail", and permissions
should be -rw-rw (i.e. rw by user and group, no world permissions).
I suspect that at some point you have upgraded or changed your distro
and although you have used the same username, the UID of that user has
changed - hence the mail spool file is called the correct thing, but is
not owned by the correct user.
P.
___
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] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]
To enter the list, I need to send from the right mail account.
On Tue, 2012-10-30 at 12:33 +, 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//.local/share/evolution/mail/spool/: (No such file or directory)
/home//.local/share/evolution/mail/smtp/:465 (No such file or
directory)
stat64("/var/mail/" etc = 0
open("/var/mail/", O_RDONLY|O_LARGEFILE) = 33
Several times: (varying 6 char extension to .
stat64("/var/mail/", {st_mode=S_IFREG|0660, st_size=95669778, ...}) = 0
open("/var/mail/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/'
(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'
(evolution:16230): camel-WARNING **: CamelVTrashFolder::synchronize_sync() set
its GError but then reported success
(evolution:16230): camel-WARNING **: Error message was: Error storing 'mailbox:
//INBOX (spool)': Could not lock '/var/mail/'
(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: //INBOX (spool)': Could not lock '/var/mail/'
(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!
> > > > > spool:/var/mail/username - do you see that?
> > > >
> > > > Yes I see it now: spool:///var/mail/"username"
> > > > 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/
> If you need to play with the gconf entries, use gconf-editor
I changed to two slashes and one slash, same or worse problem.
___
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] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]
> > I'm just saying the when I created the new mbox file account after > removing the old, this directory was created, containing these files. Yes, because Evo needs somewhere to store the indexes for that account. > The pop account I have is also having a strange name, but that directory > contains: folders.db, uid-cache and a subdirectory cache containing the > actual mail files (in maildir format?). POP needs a different set of internal files, which is stored in that directory. 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. > > > 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 Will give you an output of every single file that Evolution accesses - pipe the output of the command to a file then use grep to see if the file you want is being accessed. > > > Note though, the file will NOT be updated because you haven't > > changed anything in it. > > Evo is reporting several thousands of mails available but cannot find > the mails themselves. Is there actually that many messages in the spool file? > > > Have you even tried running Evolution from the command line to see if > > there are any errors reported? Have you tried doing it with debugging > > turned on? > > From command line yes. That is where the message below comes from: > (evolution:8019): evolution-mail-WARNING **: Failed to refresh folders: > Error storing 'mailbox: //INBOX (spool)': Summary and folder > mismatch, even after a sync > > I have also been running evo with debugging before, but forgot it by > now. (It's not the first time there are problems with evo) How to enable > debugging info? http://projects.gnome.org/evolution/bugs.shtml > > > > > to see it. These chunks of XML are sometimes difficult to sort out, but > > > > you are looking for a line that starts " > > > In that line there should be a section looks like > > > > spool:/var/mail/username - do you see that? > > > > > > Yes I see it now: spool:///var/mail/"username" > > > It seem to be correct, why does not evo find it? > > > > > > > Does it really have three slashes in the URL? Does it have three > > slashes in the configuration within Evolution? Because it doesn't on my > > system. Perhaps that is confusing things. > > Yes, there are three slashes. The pop and imap accounts has two! Can I > edit that in some easy way, using gconftool-2? Or can I edit the > %gconf.xml file directly? > Does the config within Evolution have three slashes? Can you change it there? If you need to play with the gconf entries, use gconf-editor P. ___ 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] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]
On Tue, 2012-10-30 at 12:34 +0100, Svante Signell wrote: > (evolution:8019): evolution-mail-WARNING **: Failed to refresh folders: > Error storing 'mailbox: //INBOX (spool)': Summary and folder > mismatch, even after a sync That reminds me of famous bug 213072. Also see http://library.gnome.org/users/evolution/3.2/mail-error-folder-mismatch.html > Yes, there are three slashes. The pop and imap accounts has two! Can I > edit that in some easy way, using gconftool-2? Or can I edit the > %gconf.xml file directly? You can use gconftool-2 (command line) or gconf-editor (UI). andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ 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] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]
On Tue, 2012-10-30 at 10:39 +, Pete Biggs wrote: > > > > > > > > > > They are the normal indexing and config files for mail accounts - they > > > > > don't contain any emails. > > > > > > > > It seem like evo is looking for the mails in that directory?? > > > > > > I can't see anywhere where you say how you know it's looking in that > > > directory? > > > > As I wrote above, that directory is the latest updated under .local: > > ~/.local/share/evolution/mail/ > > containing the above mentioned files. Among the files the folders.db > > (but as you say, not real mbox files). > > !! So you are basing your assertion that Evolution is looking in the > wrong place for the mail on the fact that a directory under .local > happens to be updated at the same time - the directory that contains all > the indexing for the account in question - indexing that *will* be > updated when the account is accessed?? I'm just saying the when I created the new mbox file account after removing the old, this directory was created, containing these files. The pop account I have is also having a strange name, but that directory contains: folders.db, uid-cache and a subdirectory cache containing the actual mail files (in maildir format?). > 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. > Note though, the file will NOT be updated because you haven't > changed anything in it. Evo is reporting several thousands of mails available but cannot find the mails themselves. > Have you even tried running Evolution from the command line to see if > there are any errors reported? Have you tried doing it with debugging > turned on? >From command line yes. That is where the message below comes from: (evolution:8019): evolution-mail-WARNING **: Failed to refresh folders: Error storing 'mailbox: //INBOX (spool)': Summary and folder mismatch, even after a sync I have also been running evo with debugging before, but forgot it by now. (It's not the first time there are problems with evo) How to enable debugging info? > > > > > > > > > > > It really sounds as though there is something up with your > > > > > configuration > > > > > somewhere. Can I suggest that you create another Unix user with a > > > > > clean > > > > > configuration and try the same thing. > > > > > > Did you do this? > > > > No I did not, I don't want to clutter my computer with another user > > (will do that if really necessary). > > So rather than try the debugging steps to attempt to isolate your > problem you would prefer to keep your filesystem looking pretty? You do > realise that you can delete the account (and all its files) afterwards? In will try next time I have access to that box again, yes. > > > > > > > > I did not find any mail accounts when finally discovering evolution > > > > under org/gnome/evolution. Seems like the version there is 3.4.0 while > > > > 3.4.4 is installed. Under org/gnome/evolution/mail I found a lot of > > > > settings, but nowhere any info about my pop and imap accounts. However, > > > > under default account there was a _very_ old account name no longer in > > > > use. It does not seem to be editable in dconf?? How to change that if > > > > needed? > > > > > > You change it from within Evolution. > > > > OK, and it looks like dconf does not find anything useful. > > Yes, because it uses gconf - everything will be switched to dconf soon. 3.6? This one will definitely not be part of Debian/Wheezy. > > > to see it. These chunks of XML are sometimes difficult to sort out, but > > > you are looking for a line that starts " > > In that line there should be a section looks like > > > spool:/var/mail/username - do you see that? > > > > Yes I see it now: spool:///var/mail/"username" > > It seem to be correct, why does not evo find it? > > > > Does it really have three slashes in the URL? Does it have three > slashes in the configuration within Evolution? Because it doesn't on my > system. Perhaps that is confusing things. Yes, there are three slashes. The pop and imap accounts has two! Can I edit that in some easy way, using gconftool-2? Or can I edit the %gconf.xml file directly? ___ 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] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]
> > > > > > > > They are the normal indexing and config files for mail accounts - they > > > > don't contain any emails. > > > > > > It seem like evo is looking for the mails in that directory?? > > > > I can't see anywhere where you say how you know it's looking in that > > directory? > > As I wrote above, that directory is the latest updated under .local: > ~/.local/share/evolution/mail/ > containing the above mentioned files. Among the files the folders.db > (but as you say, not real mbox files). !! So you are basing your assertion that Evolution is looking in the wrong place for the mail on the fact that a directory under .local happens to be updated at the same time - the directory that contains all the indexing for the account in question - indexing that *will* be updated when the account is accessed?? Have you actually looked to see if the actual spool file is accessed at all? Note though, the file will NOT be updated because you haven't changed anything in it. Have you even tried running Evolution from the command line to see if there are any errors reported? Have you tried doing it with debugging turned on? > > > > > > > > It really sounds as though there is something up with your configuration > > > > somewhere. Can I suggest that you create another Unix user with a clean > > > > configuration and try the same thing. > > > > Did you do this? > > No I did not, I don't want to clutter my computer with another user > (will do that if really necessary). So rather than try the debugging steps to attempt to isolate your problem you would prefer to keep your filesystem looking pretty? You do realise that you can delete the account (and all its files) afterwards? > > > > > > I did not find any mail accounts when finally discovering evolution > > > under org/gnome/evolution. Seems like the version there is 3.4.0 while > > > 3.4.4 is installed. Under org/gnome/evolution/mail I found a lot of > > > settings, but nowhere any info about my pop and imap accounts. However, > > > under default account there was a _very_ old account name no longer in > > > use. It does not seem to be editable in dconf?? How to change that if > > > needed? > > > > You change it from within Evolution. > > OK, and it looks like dconf does not find anything useful. Yes, because it uses gconf - everything will be switched to dconf soon. > > > > to see it. These chunks of XML are sometimes difficult to sort out, but > > you are looking for a line that starts " > In that line there should be a section looks like > > spool:/var/mail/username - do you see that? > > Yes I see it now: spool:///var/mail/"username" > It seem to be correct, why does not evo find it? > Does it really have three slashes in the URL? Does it have three slashes in the configuration within Evolution? Because it doesn't on my system. Perhaps that is confusing things. P. ___ 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] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]
On Mon, 2012-10-29 at 10:05 +, Pete Biggs wrote: > > > > > > > > > > I was waiting for the latest bugfix release to see if the local > > > > > mailbox > > > > > spool problem was solved. Unfortunately it was not :( Local mails are > > > > > delivered to /var/mail/ and these are the settings used for > > > > > the local mail account in evo. However, evo looks for this mailbox > > > > > file > > > > > at ~/.local/share/evolution/mail/ > > > > > containing the following files: INBOX.ibex.index.data, > > > > > INBOX.ibex.index, > > > > > INBOX.cmeta, folders.db > > > > > > They are the normal indexing and config files for mail accounts - they > > > don't contain any emails. > > > > It seem like evo is looking for the mails in that directory?? > > I can't see anywhere where you say how you know it's looking in that > directory? As I wrote above, that directory is the latest updated under .local: ~/.local/share/evolution/mail/ containing the above mentioned files. Among the files the folders.db (but as you say, not real mbox files). > > > > > It really sounds as though there is something up with your configuration > > > somewhere. Can I suggest that you create another Unix user with a clean > > > configuration and try the same thing. > > Did you do this? No I did not, I don't want to clutter my computer with another user (will do that if really necessary). > > If it works, then you should > > > delete the configuration from within Evolution, then close Evo and check > > > in gconf (or is it dconf for 3.4) that everything has gone, then delete > > > the corresponding directory in .local/share/evolution/mail. You should > > > then have a clean configuration and you can recreate the account with > > > Evolution. > > > > I did not find any mail accounts when finally discovering evolution > > under org/gnome/evolution. Seems like the version there is 3.4.0 while > > 3.4.4 is installed. Under org/gnome/evolution/mail I found a lot of > > settings, but nowhere any info about my pop and imap accounts. However, > > under default account there was a _very_ old account name no longer in > > use. It does not seem to be editable in dconf?? How to change that if > > needed? > > You change it from within Evolution. OK, and it looks like dconf does not find anything useful. > It looks like the account information is in gconf - the key > is /apps/evolution/mail/accounts - that is populated with XML blobs > describing each account. Do > > gconftool-2 -g /apps/evolution/mail/accounts > > to see it. These chunks of XML are sometimes difficult to sort out, but > you are looking for a line that starts " In that line there should be a section looks like > spool:/var/mail/username - do you see that? Yes I see it now: spool:///var/mail/"username" It seem to be correct, why does not evo find it? ___ 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] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]
> > > > > > > > I was waiting for the latest bugfix release to see if the local mailbox > > > > spool problem was solved. Unfortunately it was not :( Local mails are > > > > delivered to /var/mail/ and these are the settings used for > > > > the local mail account in evo. However, evo looks for this mailbox file > > > > at ~/.local/share/evolution/mail/ > > > > containing the following files: INBOX.ibex.index.data, INBOX.ibex.index, > > > > INBOX.cmeta, folders.db > > > > They are the normal indexing and config files for mail accounts - they > > don't contain any emails. > > It seem like evo is looking for the mails in that directory?? I can't see anywhere where you say how you know it's looking in that directory? > > > It really sounds as though there is something up with your configuration > > somewhere. Can I suggest that you create another Unix user with a clean > > configuration and try the same thing. Did you do this? > If it works, then you should > > delete the configuration from within Evolution, then close Evo and check > > in gconf (or is it dconf for 3.4) that everything has gone, then delete > > the corresponding directory in .local/share/evolution/mail. You should > > then have a clean configuration and you can recreate the account with > > Evolution. > > I did not find any mail accounts when finally discovering evolution > under org/gnome/evolution. Seems like the version there is 3.4.0 while > 3.4.4 is installed. Under org/gnome/evolution/mail I found a lot of > settings, but nowhere any info about my pop and imap accounts. However, > under default account there was a _very_ old account name no longer in > use. It does not seem to be editable in dconf?? How to change that if > needed? You change it from within Evolution. It looks like the account information is in gconf - the key is /apps/evolution/mail/accounts - that is populated with XML blobs describing each account. Do gconftool-2 -g /apps/evolution/mail/accounts to see it. These chunks of XML are sometimes difficult to sort out, but you are looking for a line that starts "spool:/var/mail/username - do you see that? P. ___ 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] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]
On Fri, 2012-10-26 at 15:30 +0100, Pete Biggs wrote: > > On Thu, 2012-10-25 at 11:34 +0200, Svante Signell wrote: > > > severity 640851 serious > > > found 640851 3.4.3-1 > > > found 640851 3.4.4-1 > > > thanks > > > > > > I was waiting for the latest bugfix release to see if the local mailbox > > > spool problem was solved. Unfortunately it was not :( Local mails are > > > delivered to /var/mail/ and these are the settings used for > > > the local mail account in evo. However, evo looks for this mailbox file > > > at ~/.local/share/evolution/mail/ > > > containing the following files: INBOX.ibex.index.data, INBOX.ibex.index, > > > INBOX.cmeta, folders.db > > They are the normal indexing and config files for mail accounts - they > don't contain any emails. It seem like evo is looking for the mails in that directory?? > > > > > > Removing these files and restarting evo does not help: evo complains > > > about: "Summary and folder mismatch, even after a sync" > > > In the settings the local account is flagged as of type spool and for > > > Receiving Email the setting is: Standard Unix mbox spool file. > > > > More information: Evolution tries to store the mailbox entry > > at //INBOX which doesn't exist, when the mbox file is > > at /var/mail/ . That filename is given in the evo settings for > > that mail account, but is not honored?? > > > > (evolution:8019): evolution-mail-WARNING **: Failed to refresh folders: > > Error storing 'mailbox: //INBOX (spool)': Summary and folder > > mismatch, even after a sync > > > > As far as I can see what you are trying to do works fine on my box (Evo > 3.4.4 on FC17) - i.e. I can create an account of type "Standard Unix > mbox spool file" and point it at /var/spool/mail/ and it > displays the mail in the mail spool. I deleted the mbox account, the directory and created a new account in evo. Same problem! > It really sounds as though there is something up with your configuration > somewhere. Can I suggest that you create another Unix user with a clean > configuration and try the same thing. If it works, then you should > delete the configuration from within Evolution, then close Evo and check > in gconf (or is it dconf for 3.4) that everything has gone, then delete > the corresponding directory in .local/share/evolution/mail. You should > then have a clean configuration and you can recreate the account with > Evolution. I did not find any mail accounts when finally discovering evolution under org/gnome/evolution. Seems like the version there is 3.4.0 while 3.4.4 is installed. Under org/gnome/evolution/mail I found a lot of settings, but nowhere any info about my pop and imap accounts. However, under default account there was a _very_ old account name no longer in use. It does not seem to be editable in dconf?? How to change that if needed? ___ 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] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]
> On Thu, 2012-10-25 at 11:34 +0200, Svante Signell wrote: > > severity 640851 serious > > found 640851 3.4.3-1 > > found 640851 3.4.4-1 > > thanks > > > > I was waiting for the latest bugfix release to see if the local mailbox > > spool problem was solved. Unfortunately it was not :( Local mails are > > delivered to /var/mail/ and these are the settings used for > > the local mail account in evo. However, evo looks for this mailbox file > > at ~/.local/share/evolution/mail/ > > containing the following files: INBOX.ibex.index.data, INBOX.ibex.index, > > INBOX.cmeta, folders.db They are the normal indexing and config files for mail accounts - they don't contain any emails. > > > > Removing these files and restarting evo does not help: evo complains > > about: "Summary and folder mismatch, even after a sync" > > In the settings the local account is flagged as of type spool and for > > Receiving Email the setting is: Standard Unix mbox spool file. > > More information: Evolution tries to store the mailbox entry > at //INBOX which doesn't exist, when the mbox file is > at /var/mail/ . That filename is given in the evo settings for > that mail account, but is not honored?? > > (evolution:8019): evolution-mail-WARNING **: Failed to refresh folders: > Error storing 'mailbox: //INBOX (spool)': Summary and folder > mismatch, even after a sync > As far as I can see what you are trying to do works fine on my box (Evo 3.4.4 on FC17) - i.e. I can create an account of type "Standard Unix mbox spool file" and point it at /var/spool/mail/ and it displays the mail in the mail spool. It really sounds as though there is something up with your configuration somewhere. Can I suggest that you create another Unix user with a clean configuration and try the same thing. If it works, then you should delete the configuration from within Evolution, then close Evo and check in gconf (or is it dconf for 3.4) that everything has gone, then delete the corresponding directory in .local/share/evolution/mail. You should then have a clean configuration and you can recreate the account with Evolution. P. ___ 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] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]
Hi, Forwarding this problem to the list. Maybe somebody has a solution/explanation? Is it fixed for 3.6.x? If so, is a simple backport possible? Thanks! Forwarded Message From: Svante Signell Reply-to: svante.sign...@telia.com To: 640...@bugs.debian.org Subject: Re: local mail spool still unaccessible with evo 3.4.4.-1 Date: Fri, 26 Oct 2012 08:45:09 +0200 On Thu, 2012-10-25 at 11:34 +0200, Svante Signell wrote: > severity 640851 serious > found 640851 3.4.3-1 > found 640851 3.4.4-1 > thanks > > I was waiting for the latest bugfix release to see if the local mailbox > spool problem was solved. Unfortunately it was not :( Local mails are > delivered to /var/mail/ and these are the settings used for > the local mail account in evo. However, evo looks for this mailbox file > at ~/.local/share/evolution/mail/ > containing the following files: INBOX.ibex.index.data, INBOX.ibex.index, > INBOX.cmeta, folders.db > > Removing these files and restarting evo does not help: evo complains > about: "Summary and folder mismatch, even after a sync" > In the settings the local account is flagged as of type spool and for > Receiving Email the setting is: Standard Unix mbox spool file. More information: Evolution tries to store the mailbox entry at //INBOX which doesn't exist, when the mbox file is at /var/mail/ . That filename is given in the evo settings for that mail account, but is not honored?? (evolution:8019): evolution-mail-WARNING **: Failed to refresh folders: Error storing 'mailbox: //INBOX (spool)': Summary and folder mismatch, even after a sync ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
