ntozier - responses belowWebservers
cannot connect to a mail server with out permission to connect to send
mail. In Exchange terms this is called a send connector.Documentation on setting up a send connector can be found here:https://docs.microsoft.com/en-us/exchange/plan-and-deploy/post-installation-tasks/configure-mail-flow-and-client-accessEverything looks to be setup correctly as per the articleWindows client? You mean Outlook? Outlook doesn't talk IMAP. It talks MAPI.No, not Outlook for the reason you mention. I used the W10 Mail Client, however, it seems smarter than me and seems to be using MAPI rather than iMAP even tho that's what I intiallly selected.I'm now using Thunderbird which connects successfully with the following settingsPort 993Connection Security - SSL/TLSAuthentication method - Normal PasswordStarting
circa Exchange 2007 (iirc) both IMAP/POP were disabled by default and
had to be enabled at the server level and/or the user level.Mailbox is IMAP enabledAutocron collects emails?And when you run cron it does not?Yes, just retested, all test tickets received and responses sent back to originatorKevinTheJedi - response belowI'm not brave enough to ssh into the Synology and edit the Cron directly. I'm therefore using the builtin Task Scheduler with this String/usr/local/bin/php56 /volume1/web/osticket/upload/api/cron.phpFor what its worth, it took me a few attempts to get the right string so I could see errors being generated in the output. As soon as I hit the "right" string, no output was logged in the task and the Cron Job log entry appeared in the osTicket System log.Contd in next post