Hi Gang! We have been plagued by a mail fetcher error for some time now and I suspect that it has to do with our sub emails and not our full support@ email address as we are still receiving tickets just fine. However, it has recently started bogging down performance. We currently have three email address from our host server tied to OSticket: noreply@ alerts@and support@ this one being the main email address for tickets. the first two email addys are set to disable email fetching but still configured to delete the messages from the host email. When I originally did the configuration, I left those as set to disable fetching and do nothing with fetched emails. When we started receiving the email fetcher error I changed those two email addys to delete fetched messages and the error stopped for about two weeks. It has recently started again my thought was to enable fetching to eliminate the error. However when I attempt to do this I get a Log in Failed: check POP settings error and a POP3 connection broken in response error. When I searched the forums I did not see anything specific to the mail fetcher error so any help would be greatly appreciated. I suspect this is a configuration error on my part but it may be a host email issue as well... I am a bit new to all this so I apologize if that is not very clear. Anyway the version we are using is osTicket Versionv1.9.1 (0e29c8d)Server SoftwareApache/2.2.22 (Debian)PHP Version5.4.4-14+deb7u10MySQL Version5.5.37 Has anyone else experienced this mail fetcher error? It happens about every 5 minutes. I did not do the original set up with the host email and the install for OS but I have done the majority of the configuration process.
If you aren't doing anything with the emails noreply@ and alerts@ you could remove the mail settings and just prevent them from trying to check mail. (I seen to recall there being a enable disable radial in the mail settings you could try to toggle them off.)
I will look into that and see if it helps at all. Thank you!
You're very welcome. I'll leave this thread open so please post a follow up and let us know how you make out.
We have actually called this one into support and are awaiting a follow up on this error. I will post the solution. Thank you again for your help.
So we were able to find out that our fastmail contained had the root of the problem with an email that was not able to be auto-deleted and it was sitting in our archive server and could not be fetched. We have resolved the issue. I apologize; this was not an OSTicket issue at all. Thank you for the assistance though. It is much appreciated.
Great you resolved your issue!@[deleted]:I guess this thread can be closed / marked as resolved
@Stephanie_Johnson thanks for following up with us. Please do not hesitate to start a new thread if you have another question, comment, concern, query, wonder, etc. :)