After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 664224 - error occurred during post
error occurred during post
Status: RESOLVED DUPLICATE of bug 638307
Product: evolution
Classification: Applications
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-11-16 19:54 UTC by James Piccinelli
Modified: 2011-12-29 08:05 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description James Piccinelli 2011-11-16 19:54:02 UTC
Error Message
Message was sent but an error occurred during post processing. 
Failed to append to mbox:///home/jim/.local/share/evolution/mail/local"sent : invalid folder URI 'mbox:///home/jim/.local/share/evolution/mail/local"sent'
Comment 1 Akhil Laddha 2011-11-17 03:48:14 UTC
What's the evolution version Menu -> Help -> About ? 
Please check sent folder setting in edit -> preferences -> edit account -> defaults tab-> special folder

mostly duplicate of bug 638307
Comment 2 James Piccinelli 2011-11-17 19:08:09 UTC
Evolution 3.2.0

I enabled jim@localhost and pointed the "drafts" and "sent" to "drafts/on this computer" and "sent/on this computer".  I sent a message and didn't get an error.  I'll try a few more messages and if the problem is gone I'll close the bug report.
Comment 3 James Piccinelli 2011-11-18 22:26:00 UTC
(In reply to comment #2)
> Evolution 3.2.0
> 
> I enabled jim@localhost and pointed the "drafts" and "sent" to "drafts/on this
> computer" and "sent/on this computer".  I sent a message and didn't get an
> error.  I'll try a few more messages and if the problem is gone I'll close the
> bug report.


The error message is no longer appearing after the above changes were made.
Comment 4 Akhil Laddha 2011-12-29 08:05:24 UTC

*** This bug has been marked as a duplicate of bug 638307 ***