| Summary | Possibly malformed e-mail not handled properly |
| Queue | Horde Framework Packages |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | mrubinsk (at) horde (dot) org |
| Requester | arjen+horde (at) de-korte (dot) org |
| Created | 01/22/2018 (2723 days ago) |
| Due | |
| Updated | 02/11/2018 (2703 days ago) |
| Assigned | |
| Resolved | 02/11/2018 (2703 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
Assigned to Michael Rubinsky
State ⇒ Resolved
by the error fixed here:
https://github.com/horde/Imap_Client/commit/4666bf5d32372955a32f9efcc6c083812fb202d3
I've added some code that will treat the PARSE error the same as a CTE
error with respect to a binary fetch in that it will try it again
without the binary extension before failing.
New Attachment: Imap_Client_Socket.patch
* IMAP: When BINARY FETCH finds a broken mails, send [PARSE] error
instead of [UNKNOWNCTE]
And lo-and-behold, if I apply the attached patch, all seems to be well
again. I doubt this is the correct way to deal with the above change
however, as this will bluntly treat a PARSE error as UNKNOWNCTE and I
really suck at PHP programming.
You have been warned...
New Attachment: imap.log
just fine. Curiously enough, Horde only has problems in messages from
one mailinglist.
than a month ago) could be read just fine, now no longer do and lead
to the dreaded communication failure with the server.
New Attachment: horde.log
Milestone ⇒
State ⇒ Unconfirmed
New Attachment: 1516614291.M217355P23993.mail,S=7835,W=7965_2,S
Patch ⇒ No
Queue ⇒ Horde Framework Packages
Summary ⇒ Possibly malformed e-mail not handled properly
Type ⇒ Bug
Priority ⇒ 1. Low
interface and stops ActiveSync from synchronizing the folder it is in.
After removing it from the folder, all is well again.