Genereal suggestion | Best practice

[aj-saini]

I would like to know where/how are everyone else using free scout,

we tried using it in production but too many fetch email errors happening all time randomly

can someone please share their best configuration/setup for example
we tried AWS lightsnails, in house proxmox servers hypervisor and also docker containers - they are have fetching errors delay or just very slow,
our email provider is msft office 365,

can someone please share production level setup which is reliable and best practices so that we can that shot overall i really like the freescout interface and powerful modules

But i just need help someone point me in the right direction

Thank you

[freescout-helpdesk]

What kind of errors are you having?

[aj-saini]

[aj-saini]

[aj-saini]

Hi freescout-helpdesk team,

Please see the errors above, can you please also tell me the optimal recommended setup where you find people have least amount of errors, recommended hosting provider, operation system or anything else i should be focusing on moving forward

[freescout-helpdesk]

If there is a chance simply use some other email provider. No other email provider gives so much headache to users as MS Office 365.

[aj-saini]

interesting good to know, unfortunately that would be very very hard, any luck with the above errors ?

[avenjamin]

@aj-saini We use MS 365 and do get the occasional fetch error just as you're seeing.

However FreeScout is working great in our production environment and we haven't actually had any issues with mail fetching or sending despite the messages you see.

I suggest testing it out and you may find the fetch errors settle down after a while.
We average, per day, 10 new tickets, 20-30 customer messages, 10 agent replies.
I haven't had a fetch error for some time now.

In case it helps I'm running our instance on an Ubuntu VM with PHP 8.0.
I'd also recommend staying up to date as @freescout-helpdesk is maintaining the code fairly actively.

[freescout-helpdesk]

Also try to increase Fetching interval in "Manage » Mail Settings".

[aj-saini]

@avenjamin
Can you please share your Ubuntu version you downloaded or prefer,

Also by any chance you know how much delay your getting in fetching emails,

Is it every one minute ?

[aj-saini]

Also is it Ubuntu VM - server or desktop Gui edition,

I am trying to minimize failure and looking for best option

[aj-saini]

• • • • • php /var/www/html/artisan schedule:run >> /dev/null 2>&1 - this cmd runs/update the whole application once every minute, browser notifications fetch emails and blah blah

what if i run only this cmd php artisan freescout:fetch-emails every 5 seconds for example > put it under a script and execute every 5 seconds,

one of the reason i believe freescout is "slow" it makes a new connection every minute
authenticates then fetch emails and then close connection ?

Please feel free to comment if above is a bad idea

[freescout-helpdesk]

What are you trying to achieve?

Proper configuration is described in https://github.com/freescout-helpdesk/freescout/wiki/Installation-Guide

[aj-saini]

So one of the only issue I have noticed with freescout is the every minute fetching is very slow,

Why can we not run or not set by default "php artisan freescout:fetch-emails" to run like every 5 to 10 seconds

I am sure freescout developers are smarter then me, but i am curious to why it was not setup

Thank you

[freescout-helpdesk]

1. Standard cron does not allow to run commands more often than every minute.

2. If you will connect by IMAP too often your mail server may start blocking FreeScout connections via IMAP.

[minghuiyu]

Reduce fetching email frequency, every 5 minutes will be much better.

If you have multiple emails to fetch (most likely), don't fetch all emails at the same time, fetching email one at a time.

You don't want a new email fetching process when the previous process is in a limbo state, you will likely get a high CPU usage issue then.