Page 1 of 1

moved emails in edit mode!

PostPosted: Wed Mar 28, 2018 4:37 am
by ecotao
Lately, I have noticed that ALL emails that I move with X1 to my archive folders end up in edit mode!
If I work from Outlook and drag and drop to the same folder, the emails are "normal" received emails. So it is not a folder bug - it only happens to files moved with X1.
This is a major bug, as I cannot find a way to reverse emails in edit mode.
The emails have the the pen and paper icon, but were moved from my inbox as normal received email.

Due to this mode "reply" is blanked off and if you popout email it has original senders email at top as sender and not my email. If you send it, the archive is deleted as if it were an outbox.

I have lost emails and data due to this.

I moved files to an empty folder from the inbox with X1 and all ended up in edit mode. As mentioned, drag and drop to the same folder withing Outlook and the bug does not occur.

Re: moved emails in edit mode!

PostPosted: Sat Apr 21, 2018 7:01 am
by ecotao
I tested one email today and the BUG remains.
Any email moved with X1 to another folder ends up in edit mode as if it is to be sent and the sender email address is in the sender address.

This is a MAJOR BUG using X1 and Outlook.

Re: moved emails in edit mode!

PostPosted: Tue Apr 24, 2018 11:53 am
by Jul.Alx
ecotao wrote:I tested one email today and the BUG remains.
Any email moved with X1 to another folder ends up in edit mode as if it is to be sent and the sender email address is in the sender address.

This is a MAJOR BUG using X1 and Outlook.


Same issue here. Pretty annoying. I opened a ticket to Support as well.

Re: moved emails in edit mode!

PostPosted: Fri May 04, 2018 9:57 am
by fsandolo
I am having the same problems. Any email moved cause the email to go into edit mode. I move massive amount of emails at the end of the week as part of my organization strategy.

Can/should I revert back to an older version of X1 until this bug is fixed?

Frank.

Re: moved emails in edit mode!

PostPosted: Mon May 07, 2018 12:37 pm
by cscott
Hi all,

We're aware of this bug and are working towards a fix.