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 328555 - "Could not append message" (ms exchange)
"Could not append message" (ms exchange)
Status: RESOLVED DUPLICATE of bug 271567
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.4.x
Other All
: Normal normal
: 2.5
Assigned To: Sankar P
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2006-01-25 10:11 UTC by Christoph Müller
Modified: 2006-02-27 14:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Attachments
one not moveable message (2.49 KB, application/x-compressed-tar)
2006-01-25 10:14 UTC, Christoph Müller
Details
debug trace (1006 bytes, application/x-compressed-tar)
2006-01-25 10:29 UTC, Christoph Müller
Details

Description Christoph Müller 2006-01-25 10:11:38 UTC
Please describe the problem:
When trying to move a message to a folder on the ms exchange server the
following error occurs: "Could not append message".
(the message was previous fetched via POP3 by evolution).

This applies to manually movement as well as automatically movement by filter rules.

Not all messages are affected, but some are.

Steps to reproduce:
1. fetch email via pop3
2. try to move it to a folder on the exchange server



Actual results:
the following error occurs: "Could not append message".

Expected results:


Does this happen every time?
No. only some messages are affected.

Other information:
Where can I upload one of these erroneous messages?
Comment 1 Christoph Müller 2006-01-25 10:14:23 UTC
Created attachment 58071 [details]
one not moveable message

this is one message i was unable to move to the exchange-folder.
Comment 2 Christoph Müller 2006-01-25 10:29:17 UTC
Created attachment 58072 [details]
debug trace

A debug trace I tried to create.
Comment 3 Sankar P 2006-02-17 06:12:16 UTC
Workaround: Instead of copying the message, Forward the message as attachment to yourself(exchange-id) so that you can view it. 

The server seems to not like some mails. Server thrwos BAD-REquest error when we try to copy the mail.

=======
400 Bad Request
E2k-Debug: 0xb4b100a8 @ 1140156746
Date: Fri, 17 Feb 2006 06:19:32 GMT
Connection: close
Content-Length: 34
Content-Type: text/html


(evolution-exchange-storage:4967): exchange-mail-WARNING **: appended_message: 400
======

Should investigate further..... Assigning to myself and trying to fix.

Comment 4 Sankar P 2006-02-17 08:24:55 UTC
When I tried to view the mail (that you have attached) in OWA, it complained that the mail might contain Viruses :(

Dont know if this is preventing the server from appending-the-message.

*Sigh* Neither Outlook nor OWA seems to have a way to import a single mail so as to test this mail.
Comment 5 Christoph Müller 2006-02-17 09:36:00 UTC
I also have the "Bad Request" response (captured via ethereal).
It contains as reason "Invalid URL".

this is the http request line I sniffed:
"PUT /exchange/pisi/Posteingang/devel/l4-hackers/Re:%20Instances%20of%20lazy%20scheduling%20and%20timeslice%20donation%20in%20L4%09implementations.EML HTTP/1.1"

There is a %09 in the URL. Maybe this is the problem.
If I edit the mail and cut the topic after 'donation', it works.

maybe this helps.
Comment 6 Sankar P 2006-02-27 14:19:57 UTC

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