• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

cron ttsmailparse.php fails

iHuman

Basic Pleskian
Cron runs ttsmailparse.php and returns the following error through notifications:

Failed to open mailbox: Login failed.,Login failed.,Login failed.,Too many login failures

I am assuming some login that ttsmailparse.php requires is inaccurate - but have no idea where this should be set.

The TTS mailgate info / login is correct.

Any suggestions?

Thanks for your assistance.

elaine
 
Elaine,

Did you do anything prior to it starting up? We changed
the hostname on the server, then it popped up with those
errors in e-mail floodin gin until we disabled the Mail Gate
in Help Desk while we sort this out.

One thing we noticed beyond the timing of it starting up
was that inside the error e-mails the beginning point is
saying:

'Cron <root@oldhostname>' then the long error paths. We're
trying to determine where in the Cronjobs it's being called
up because it may not be so much an error as an incorrect
mailto for errors in that cronjob? Either way something that
feeds into the Plesk Trouble Ticket parser PHP routine here
needs to be changed. We're just not sure if that's something
in the Admin Panel's we all can get to and update, if it's
something you need to SSH in and deal with or if someone
really blundered in programming and it's inside the PHP file
itself and we're supposed to crack, edit & recompile?

I can't believe it's the latter so somewhere there's a conf
file or GUI setting needed to correct the problem. We even
updated the information in the Mail Gate to ensure the server
was correct, etc. as you did. Also tried using another domain
and then an outside domain - all DOA.

We're open for suggestions as well but let me know if you
did something prior to that starting up!

Dave
 
Back
Top