Inbound Email - Malformed header detected

[randyklein]

I have my inbound email properly configured, and when I test the connection, it completes without issue. Up until recently, my inbound email worked perfectly fine. I've made no recent changes, but my email stopped working. I found the EspoCRM logs in the data/logs folder, and I'm seeing the following error each time the cron job runs:

[2015-09-07 00:34:02] Espo.ERROR: InboundEmail 54a7204353ed0 (Get Message): [0] Malformed header detected [] []

I've tried clearing the cache, and I've tried completely clearing out the inbox of the email account. Neither have worked. I'm at a loss. Thanks for any help.

[yuri]

Hi

This should be fixed in the 3.6.* version. What the version do you use?

[randyklein]

I'm on 3.6.2. Still seeing the issue. I've recently upgraded (incrementally) from 3.2 to 3.6.2. I noticed the issue after the upgrade.

[yuri]

Can you confirm that emails now not being imported at all? Did it stuck with that bad email and now doesn't import any emails anymore?

[yuri]

Can you try to apply this small fix https://github.com/espocrm/espocrm/c...c7f1438c03d622
Please let me know about result.

Thanks

[randyklein]

Unfortunately, still getting the exact same message: [2015-09-10 13:27:01] Espo.ERROR: InboundEmail 54a7204353ed0 (Get Message): [0] Malformed header detected [] []

Was I supposed to clear the cache after changing the files? I didn't do that.

[yuri]

And you don't receive other emails, right?

[randyklein]

Correct, it's not importing any emails from the mailbox. I tried setting up both the personal email, and the group email. Neither imported emails.

[randyklein]

I quick update to this. I'm not sure exactly what's going on, but it appears to be fixed. I havent used the site in a few days (and havent made any changes), but I logged in this morning, and all of the missing emails were now imported. A week or two ago, I also tried to update the logo, but the logo that shows in the top left never actually updated. I just ignored this issue. However I also noticed this morning that the logo was also updated. I've cleared the cache many times before in trying to fix both issues, so I don't think it was that. Perhaps it's coincidence, but I'm guessing it isnt. I have absolutely no idea how this was fixed.