imap polling excessive errors

wbartlett

Hi all I recently migrated my install over to a new server and everything seems to be working OK except for my email polling - I'm now receiving the following message every time my cron job runs or I run in manually:
Excessive errors processing emails for imap.gmail.com/XXX@DOMAIN.org. Please manually check the inbox.

I am able to send mails through this same account without any problems. My server info is below:

ntozier

You would want to check the mailserver logs to see why the mailserver is rejecting the connection to collect email.
You can check the PHP error logs, but I do not think that you will find anything there.

wbartlett

Being a gmail account I'm not sure how to view those type of logs - I just did a test with my old server and it came right through without any issues - I feel like I must have missed something basic in my setup. My old server was running php 7.0 if that might make a difference.

ntozier

The old server also connected to gmail?

wbartlett

correct - I backed up my database and configuration files and followed the migration guide.

ntozier

Hmm. Well I dont think that you can look at the logs for gmail.
Try re-entering the password in the email entry in osTicket UI. (I doubt that it will do anything)
I'm not sure why one server would be able to talk to a remote server an the other not.
Maybe a local firewall, or mod_security, or SELinux, are probably the most likely culprits.
If we could get a error message from the remote server it would help narrow it down.
Did you check the PHP error logs?
Do you have the same PHP extensions enabled on both servers?

wbartlett

I'll double check the PHP extensions, and the other things - the error log for apache isn't showing any PHP errors.

wbartlett

only thing that was missing between the two for php extensions was mcrypt. I'll have to revisit this and see if something else jumps out at my tomorrow but I'm at a loss as to why this decided to stop working.

wbartlett

one other thing - I tried the auto-cron as well and even that isn't working. I feel like something on the new server must be getting in the way but I can't narrow it down