Alberto M

@James Ainsworth, thanks for the response. In fact, here this happens. With me it was not the first time a search could not find something that going with a workaround path we can find. The other day I got a colleague complaining about it as well. Should a re-index should be made in activitystream?

@Lyonel, and yes, as you can imagine, having such grinning face in things like this, one after another, from those offshore staff And... even worst: if you mouse over the emoticon, it says "GRINNING FACE"

Hello!!!

Hi. Errrrr... I know this is a futile and shallow subject but... can Hornbill be changed so that a normal smile ": )" will not result in a grinning face? This is resulting in a awkward experience very often. :| Thanks.

I'll cancel the existing request and raise a new one.

Hi. We are having an error in the workflow for a request. I found that it should be due to a situation that happens seldom that takes this workflow route - that why it never happened in the past. The cause of this error will be this flow (in the image) that I don't know why is set like this - this shouldn't be possible and should give an error when you validate the workflow. Anyway... I'll change the workflow, but I need to know how to apply this new version of the workflow to this request so we can progress with it? Thanks for any help. Alberto

Hi. What happens when I delete a timesheet category that has already historical data from timesheet entries? Cheers A.

Hi. A quick query: is there a limit on the length of time that the search works for? It seems that, when I search a workspace for something old - older than one year in this situation - older posts are ignored in the search. Cheers, Alberto

@Deen, @Victor, Thanks a lot!!

@Deen, I can see the subscription list populated now. Can you please confirm it's solved for us?

Sorry to hijack this thread... Where do I check if a specific user failed to be imported into Hornbill using LDAP?

Here not yet. I believe this will be solved in a instance by instance basis.

I'm having a lot of problems in the Service Manager. Can't access requests and other features as well!! FYI: I didn't applied the last update yet.

@jeffreysmith, @Victor, Meanwhile, we've set O365 in the outbound email configuration - again - last Monday. Yesterday morning I already had analysts complaining that emails were not being sent. I've tested myself sending an email from a request and it failed immediately, I mean, 30 seconds after sending it, the email message was already in the sent folder with "failed" status, which apparently means that no mail.outbound retry settings have been applied and they seem useless for this situation. I then rolled back the outbound email configuration to the previous one and realized that around 200 emails have been rejected yesterday morning due to this. Please check what can be done to help solving this. Regards, Alberto (this is our mail.outbound retry settings)

@jeffreysmith, @Victor, meanwhile, regarding the "Test connection" button when setting up the outbound settings, with the current button feature and O365 it's impossible to test because Outlook doesn't provide to send using different from address other than your username to log in, and this test is made using a sender do-not-reply@live.hornbill.com This is something that should be changed in this button feature.

@jeffreysmith, @Victor, FYI, the answer from MS support when we asked them about changing the emails per minute threshold in O365: "Thank you for answering the call today, as per the update from our engineering team we cannot increase the rate limit. We can only increase daily send limit as one time activity if required as of now. Engineering team further said that If you will submit messages too quickly and the send-as is denied this will count against RRL, They suggest to throttle sends to mitigate the issue." We changed a few settings in the mail.outbound settings and we will be changing our outbound configuration today although we are not convinced this will solve the issue if we hit again the 30 emails per minute threshold.

Glad to help, @Martyn Houghton

@Martyn Houghton, did you tried the same format as I (we?) use in the SQL Database Direct? 2020-07-01

@jeffreysmith, thanks for the explanation. After a quick investigation in our sent messages folder for this mailbox, it seems that, from time to time, we break this threshold, which should be normal for the thousands of users we have.

@Victor, so, it seems that, when there is a large number of outbound messages retrying one after another, it generates "a large burst within a short time period", even if you tweak the current existing setting in Hornbill.

@Victor As this seems not to work with O365, we believe Hornbill should think about a setting to manage this. The error described here:https://docs.microsoft.com/en-us/exchange/troubleshoot/send-emails/smtp-submission-improvements"554 5.2.0 STOREDRV.Submission.Exception:SubmissionQuotaExceededExceptionThis change for concurrent connections will better protect the service from large bursts of email messages that are sent by automated systems within a short time period."We believe that MS O365 is being widely used worldwide and email services that use it should be prepared to avoid "large bursts of email messages that are sent by automated systems within a short time period". If Hornbill is interested in his large customers to not have this problem, this feature should exist in Hornbill.

Should I set this to a higher amount?

@Victor, thanks for the suggestion, but we have those settings as you show here and we had a lot - really a lot! - of emails not being sent when this issue appeared after we tried to set O365 as outbound email server. So, apparently this way is not solving this issue.

Done it meanwhile, thanks

Is there anyone that can respond to this?!