cron job aborts when bad email found on POP server!

[Doug I.]

Hi,

I am posting this problem & solution here to save other kayako members from the hours of torture I had pinpointing this issue.

There is a bug with Kayako's cron job (latest version 3.11.01) when receiving email that will cause the mail parser to simply halt and not continue checking the rest of the email queue.

Kayako could certainly make the argument that the mail server should not have allowed a malformed SPAM email into the mailbox to begin with, and so I have notified the makers of the popular MailEnable Software of this issue as well.

I would still lean toward suggesting that Kayako's cron job should skip problematic emails versus simply crashing and not even recording a problem in the Kayako log file.

I have attached the malformed email source that will cause SupportSuite mail check process to fail. It took some debug log checks on the mail server side of things for me to identify that Kayako was clearly stopping the email retrieval process when it came across this mailbox message.

If someone from Kayako would be so kind to post this bug in the bug tracker, I think it will save you a lot of headaches when others claim that their POP mail is suddenly not retrieving messages.

Later,
Doug

[Jamie Edwards]

Hi Doug,

I have submitted it here; http://bugs.kayako.com/index.php?cmd=view&id=289 - I agree the parser should not crash out.

[Jamie Edwards]

Hi there,

As per: Kayako Bug Tracker - Viewing Issue #289 - Malformed spam message causes mail parser to crash

Ryan has found:

Sorry, but the parser doesn't "crash" when processing this message; it properly says that there were no recipients found and it ends up in the parser log as an error.

Can you confirm the same on 3.20.02?

[Toby H]

I believe I am seeing an alike issue, althought havent yet pin pointed it.

GIF89a
�
�€��ÿÿÿ���!ù
����,����
�
��D
�;

That is what my cron email is returning, and the cron is not working, this is a fresh install

[Toby H]

Does anyone have any ideas on this? It's kind of holding up our new site roll out

Thanks!