> 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 sh
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.
>
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
>
> > 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
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:
>
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
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
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-he
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
>
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
> >
> > 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
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?
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.
> > >
>
> > > 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
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
>
> 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: (varyi
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 lo
>
> 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
> con
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/us
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
> > > >
> > > > 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
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 u
> > > >
> > > > 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 t
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
> >
> 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
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
26 matches
Mail list logo
