imap_open mailbox flags chronological order not clarified!
Nobody has claimed this yet.
- Dominant language
- XML
- Stars
- 596
- Forks
- 890
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 55
Description
From manual page: https://php.net/function.imap-open
I was receiving the following error:
Can't do secure authentication with this server (errflg=2)
The /imap and /ssl flags were in the wrong order though this only mattered after I added the /secure flag.
(Snippet) Before / Broken:
:993/imap/ssl/secure
(Snippet) After / Working:
:993/ssl/imap/secure
I'm not sure where the original mix-up came from as this was originally programmed in my system about a decade ago.
I'm not sure how the documentation should be updated, only that it should be updated in regards to the chronological order of flags. In the interim I posted a comment with the error message and clarification to help anyone else who encounters this oddity.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the imap_open manual page linked in the issue and review how mailbox flags are documented. Clarify the relevant flag order and secure-authentication behavior using the reported broken and working snippets; done means the documentation explains the ordering clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100