Question: Compatibility with original IMAP functions

[pribeirojtm]

Hi @francescobianco

Can you please clarify what do you mean by this compatibility list?

https://php-imap2.javanile.org/compatibility.html

For example, I currently use the function imap_delete() that is not checked as compatible. Can you explain the impact?

Thanks

[francescobianco]

Hi @pribeirojtm

This page as the following mission:

This page is intended to track the compatibility of all standard PHP IMAP functions over the ones provided by PHP-IMAP2 For each function is reported a list of issues born around problems on real use cases. Please add new issue if your have some concerns with specific function. All below checked functions are tested with complex tests and will be considered an exact equivalent of the original one.

Original source here https://github.com/javanile/php-imap2/blob/test/docs/compatibility.md

Please add new issue for imap_delete if you found difference with the original one.

[glensc]

@francescobianco that is not what OP asked. OP asked what is incompatible and why the checkbox is not set.

[glensc]

however, that same page has a clause:

If your function is not checked, no problem, it works but can be effected by a small difference from the original one. Ask for support and create a new issue if your have special needs or mandatory behaviour to fix.

so, the answer to OP would be that if checkbox is not set, it's not known if it's compatible as no high test coverage.

[pribeirojtm]

Please add new issue for imap_delete if you found difference with the original one.

Hi @francescobianco , the thing is that I don't want to get a surprise on the behavior of these methods, especially the ones I currently use:

• [ ] imap_open
• [x] imap_num_msg
• [ ] imap_fetch_overview
• [x] imap_fetchstructure
• [x] imap_headerinfo
• [x] imap_fetchheader
• [ ] imap_rfc822_parse_headers
• [ ] imap_body
• [ ] imap_fetchbody
• [ ] imap_delete
• [ ] imap_expunge
• [x] imap_alerts
• [ ] imap_errors
• [x] imap_close

So, I'm a worried that somehow in any other method could break the code/functionality I have...

If you can't guarantee me the same behavior and also same input parameters and output of the unchecked methods... I think I have to find other alternatives to imap, unfortunately. The only reason I was pondering this alternative to the original imap was due the compability/functionality with oauth, that I absolutely need kind of ASAP.

[pribeirojtm]

Hi @francescobianco, can you please update us regarding what I've said above? I really appreciate the idea and effort on this project. It was a clever idea. But for us to adopt your idea, we need to have more guarantees of the behaviors of each function, the compatibility status, and so on. Thanks