Dont delete fetched messages from mailbox

Hello,

What mailbox client do you use?

Thank you.

Server: Exchange 2010 SP1
Client: MS Outlook 2010

Hello,

Clarify please, what YouTrack version do you use?
For stand-alone version, provide us with the logs (USER_HOME/.youtrack/logs). We need youtrack.log and mailbox.log .
If you are an incloud user, then, please let us know your instance URL name.

Thank you.

Stand-alone version
youtrack.log (2.8MB)
mailbox.log (492KB)

Could you please let us know, do you have any postprocessing commands in mailbaox integration configuration?
And check, please, are there amounts of similar issues created from mailbox fetching? If a postprocessing command is not executed, letter from your mailbox will be fetched again and again till command won't executed correctly.

Thank you.

You are right, the problem is in email processing commands, that is - in variable $ {from}, $ {to} and $ {cc}. I can not find documentation for the syntax of these commands.

The syntax and rules for postprocessing commands are the same as for Command Window. Please take a look at this guide http://confluence.jetbrains.com/display/YTD4/Quick+Start+Guide.+Using+Command+Window

Thank you.

and how to use the variables like $ {from}, $ {to} and $ {cc} in commands?

Take a look at example in Apply command part http://confluence.jetbrains.com/display/YTD4/Mailbox+Integration .
As I've mentioned, the same syntax as in Command Window.

If it doesn't help, please provide us with the details of a command you would like to attach and I'll provide you with the correct syntax of this command.

Thank you.

When I use the "for user fromMail $ {from}" -  rule works, but a letter from the mail still does not delete. If not used "$ {from}", then all the work without problems.

Give an example of a team that puts a problem with the executor of the cc

Hi,

We've not reprodused the use case as described in your previous letter. Please confirm that, 'fromMail' exists in your project and user is choosen.

If your would like to put recipients from the CC to a particlur custom field in the issue, then execute

ccEmail ${cc} 

It will set recipients from the CC to a custom field 'ccEmail' in your issue. Please note that ccEmail field should be created.

Thank you.

If I enter the following command: http://clip2net.com/s/5oyQgv , the message is not deleted

And if I enter the following command: http://clip2net.com/s/5oyUKd ,the message is removed

What am I doing wrong?

Hello,

I assume that was my fall, I didn't tell you mailbox variables can be used with the custom fields of 'String' type only.
So, your first case doesn't work as you try to apply this command to the Assignee field of a 'user' type.
Also, regarding you use case, you may assign an issue to every person who is not registered in YouTrack. Unfortunately, it's not possible.

Thank you.

However, the field is not of type "string" http://clip2net.com/s/5oCGpI

Yes, As I've mentioned, Assignee field is a 'user' type custom field, so it cannot be used with mailbox variables.

Yes, but the rule is processed normally. Just do not delete messages from the mailbox.

Am I correct with that, your Assignee field value is set regarding this command

Assignee ${cc}

with the email address which is on CC of the message?
Could you please provide us with the screenshot of full screen issue mode of the issue, which is created from the mailbox integration and with applied postprocessing command?
If so, that's surely incorrect behavior. But I cannot reproduce this.

Thank you.

Can I give you temporary access?

Hi,

Yes, it's possible, but it's better to provide us with the details I've asked you in previous message first.

Thank you.

Hi Andrey, can you please update us on the status of this bug?
I'm using an outlook.com (former hotmail) account for receiving bugs and YouTrack doesn't delete fetched emails from the server.
The option is marked to do so in YouTrack, and in outlook.com the checkbox that allows to do so is marked as well.

Hi Andrey. The problem has remained relevant. It may still give you temporary access?

Hello medW, xoxmaman,

For a time I've investigated different cases and may confirm that the only case when your issue reproduces is when email address from cc matches the assignee value from Assignee custom field. We compare the string from ${cc} variable, and if it matches some of the value, the command can be completed. In general, the use case is wrong. It assumes that variables should be used with the custom field of a string type. Behaviour that appears, says that command completes only partly (that part which pastes variable in Assignee field), but fails on other parts. Which means that command is not completed and next action (delete fetched email from mailbox) cannot be done.
I'd like to recommend you to use variables in intelligence way in future, with the custom field of a string type.
For now, I would like to ask you to provide us with the .eml file of the letter, which is showed on a screenshots, if it's possible for you.

Thank you.