Jump to:
| Project: | IMAPWU API |
| Version: | 6.x-1.0-alpha1 |
| Component: | Code |
| Category: | support request |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | active |
| Issue tags: | error, imapwu, imapwu_api.module, Webmail Plus |
Issue Summary
We are using this with Webmail Plus and we followed all the steps in the documentation yet we end up with all these errors. This is connected to a tested and working mailserver. Permissions are set wide open. This may not be the right place for help with these errors but if anyone knows where we should inquire some direction would be much appreciated. THANKS!!!
* warning: imap_open() [function.imap-open]: Couldn't open stream {XX.XX.XXX.XXX:143}INBOX in /var/www/sites/all/modules/mail_api/contrib/imapwu_api/imapwu_api.module on line 73.
* warning: imap_status(): supplied argument is not a valid imap resource in /var/www/sites/all/modules/mail_api/contrib/imapwu_api/imapwu_api.module on line 93.
* warning: imap_check(): supplied argument is not a valid imap resource in /var/www/sites/all/modules/mail_api/contrib/imapwu_api/imapwu_api.module on line 179.
* warning: imap_fetch_overview(): supplied argument is not a valid imap resource in /var/www/sites/all/modules/mail_api/contrib/imapwu_api/imapwu_api.module on line 165.
Comments
#1
I am having the same problem on my test server:
warning: imap_open(): Couldn't open stream {:143}INBOX in /Users/joesmoe/Sites/sites/all/modules/mail_api/contrib/imapwu_api/imapwu_api.module on line 73.
warning: imap_status(): supplied argument is not a valid imap resource in /Users/joesmoe/Sites/sites/all/modules/mail_api/contrib/imapwu_api/imapwu_api.module on line 93.
warning: imap_check(): supplied argument is not a valid imap resource in /Users/joesmoe/Sites/sites/all/modules/mail_api/contrib/imapwu_api/imapwu_api.module on line 179.
warning: imap_fetch_overview(): supplied argument is not a valid imap resource in /Users/joesmoe/Sites/sites/all/modules/mail_api/contrib/imapwu_api/imapwu_api.module on line 165.
#2
same problem. subscribing.
#3
Same here... Is this module still maintained?
#4
same issue here. had this issue last year on a different server and do not recall what we did to resolve. subscribing.
#5
other posts recommend adding one of the following sets of commands or variations of these commands on the https://www.mysite.org/admin/content/mailhandler > edit mailbox > extra commands field
/ssl/novalidate-cert/notls
/novalidate-cert/tls
/novalidate-cert
BTW - none of these worked for me. But good results posted on drupal forums for adding extra commands.