Hi

I just ran new version through all the tests we have before an upgrade. It passes all tests except one. When we have a mailtrigger that saves the mail to the fileserver, it behave differently now.



When it saves the mail, it creates an additional folder I haven't seen before:



And below this is the attachments folder:



The attachments folder is empty, so it didn't save anything

Hi

I just ran new version through all the tests we have before an upgrade. It passes all tests except one. When we have a mailtrigger that saves the mail to the fileserver, it behave differently now.



When it saves the mail, it creates an additional folder I haven't seen before:



And below this is the attachments folder:



The attachments folder is empty, so it didn't save anything

Hi Thomas,

This is due to the maildomain/server, some rare ones will create very long mail IDs, but that's not the common case. However, you can temporary workaround this by enabling zetalongpaths (should be guides on google) / disable the 256 win character limitation. We are however fixing this in our next beta build.

Hi

It is great that you are fixing this! I will test as soon as I see it in the beta release notes

Hi Thomas,

could you maybe share some details how you got this work.
We tested the 9.9.9.10 Beta and we are able to setup an EWS connection with Oauth and the Testmail works.
However if we choose the connection for the Mail trigger it will fail.

We are using the URL outlook.office365.com:993 with TLS activated. Do you use the same or something different?

Hi

Does this mean you can send emails with the connection? So the smtp part work but imap fails, is that correct? Which api permissions have you gven in azure portal?

If you send a pic of your connection and api permissions, I can have a look at it later today.

I use the same settings in the connection as you. It s probable the permissions in azure that are the problem. I don't remember the specifics right now, will have to check later

I use the same settings in the connection as you. It s probable the permissions in azure that are the problem. I don't remember the specifics right now, will have to check later

Thomas,

And everyone who has any sort of mailtrigger issue - could you please download our latest beta build and see if it works better there? The issue is related to zetalongpaths (workaround is to enable that, it's easy to google how)

Please keep us updated here in the thread on if it works for you in that version or not

https://www.visualcron.c...aspx?g=Posts&t=10689 

Hi

Mailtrigger worked fine now. Thanks! This was in version 9.9.10 to be clear. I stumbled into som other issues, but I will put those in other threads.

Thomas

Hi,

thank you very much.
Yes the SMTP part works but Imap fails.
Support told us "full_access_as_app" is the only needed one.

Somehow the attachment upload is not working so here are the settings:

API:
Microsoft Graph EWS.AccessAsUser.All
Microsoft Graph openid
Microsoft Graph profile
Microsoft Graph offline_access
Office 365 Exchange Online full_access_as_app
Office 365 Exchange Online Mail.Read
Office 365 Exchange Online Mail.Send
Office 365 Exchange Online IMAP.AccessAsApp

Connection:
Adress: outlook.office365.com
Port: 993
Auth-Type: OAuth
Application ID: *
Client Secret: *
Email: visuacrontest@domain.de
Redirect URL: http://localhost:999
Tenant ID: *
Tenant Name: domain.de
Tenant Primary Domain: domain.de

The error message is: "Connection to "visualcrontest" failed when connection in Trigger "Email Trigger. Monitoring folder "default" . Save email (Always) in "Path" Save Attachment (Always)," of Job "Test Visual Cron"

Also I still wonder if it possible to have one App Connection and set different mailboxes in each mail trigger, so you don't have to create a connection / app for every mail address you use.

To be clear we are using the latest beta 9.9.10 but this thread seems still the correct one.

regards
Bastian

Hi

I would guess you can use one Azure app for multiple adresses. The app is not linked to any particular address, so I cannot see why it wouldn't work. Perhaps having multiple connections using the same redirect url could cause trouble? Support will have to answer this one.

I also have the same trouble as you adding images now. I used to be able to just copy and paste an image, but it fails now.


Regarding you connection problems. We only have the Office 365 Exchange Online full_access_as_app in azure, so it should be sufficient. Appart from that it is hard to say. Try this:

1) Check that you have the same redirect url in azure and vc.

2) Make sure that under redirect url's in azure, you have checked the 'ID tokens' checkbox

3) Instead of using default inbox in the trigger, try selecting a specific inbox.

Hi Thomas,

thank you very much, the ID Token Checkbox was the missing piece.
Not sure where I missed this information and why support couldn't´t tell me.
There is still an error with renaming the downloaded file but this is another problem and maybe just a syntax error.
So finally I can also say mail trigger does work with 9.9.10.

regards and have nice week
Bastian

Hi,

We currently have the same issue where the mail trigger (EWS connection) works for the very first time and then onwards just does not fire. Currently on version 9.9.10.
Verified that 1) Azure and VC have the same redirect URL 2) 'ID Tokens' check box is checked 3) Selecting a specific inbox did not change anything for us.

Also have some error logs if anyone can help

9/30/2022 11:01:00 AM Debug ContinueRetryConnect->Sleep done - retries left: 487 - waiting seconds: 180
9/30/2022 11:01:00 AM Debug GetStats->Started
9/30/2022 11:01:00 AM Err ContinueRetryConnect->Error occured: ReceiveMail->Error in Mail Trigger (3), ex: System.Net.WebException: The remote server returned an error: (401) Unauthorized.
at EAGetMail.MailClient.(MailServer , Byte[] ,  , MailInfo , HeaderCollection , String )
at EAGetMail.MailClient.(MailServer , String , String ,  )
at EAGetMail.MailClient.Connect(MailServer server)
at AccountParams.ComputeReader(Object , MailServer , AccountParams )
at VisualCronService.EventMailClass.ReceiveMail() in C:\git\code\VisualCronService\Triggers\Events\Mail\clsEventMail.vb:line 1575, oClient null = False - retrying to connect (retries left: 487)
9/30/2022 11:01:00 AM Debug GetStats->Completed - elapsed: 0.0038949
9/30/2022 11:01:01 AM Debug GetStats->Started
9/30/2022 11:01:01 AM Debug GetStats->Completed - elapsed: 0.0029065

We have exactly the same problem with version 9.9.10.
The connection test is successful. If the trigger is activated everything works.
After a certain time the mails are no longer triggered automatically.
If you click on the trigger and without any change on ok, the trigger is triggered again and runs for a certain time.

We have exactly the same problem with version 9.9.10.
The connection test is successful. If the trigger is activated everything works.
After a certain time the mails are no longer triggered automatically.
If you click on the trigger and without any change on ok, the trigger is triggered again and runs for a certain time.

This has been fixed in the latest official release, 9.9.12. Please download that and send us an email at support@visualcron.com if it still isn't working.

We're on VisualCron 10.0.2 and are seeing this same issue of the trigger running just fine for a few days and then even though the trigger remains active, it never triggers. When I open the job or trigger up for edit, then click ok without changing anything, the trigger quickly fires for each email it previously did not trigger on. So I see triggers on emails that came in days ago, and hours ago, and moments ago all at the same time.