Closed (won't fix)
Project:
Mailhandler
Version:
7.x-2.x-dev
Component:
Mailhandler
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
6 May 2011 at 12:34 UTC
Updated:
12 Feb 2015 at 22:23 UTC
Jump to comment: Most recent
Comments
Comment #1
danepowell commentedI assume you mean that he has a mailbox on an Exchange server that he would like to have Mailhandler fetch from, and Mailhandler is running on a separate server from the Exchange server (so local fetching is not an option)
What protocol would he like to use, if not POP3 or IMAP? Those are the only two remotely standard protocols that I'm aware of.
Comment #2
pvanerk commentedHi Dane,
He was saying I could use the Microsoft Exchange Protocol, but he couldn't mention any further details. I guess he meant MAPI (Messaging Application Programming Interface) but I don't know if that's possible. I am not really into the whole mail server thing. I asked how the managers could read their mails on their phone. They all use blackberries and they use a special blackberry server for that.
I suggested to use an internal mail address and use a forward rule to forward all the incoming mails to a gmail account. I could pick up the mails with Mailhandler from the gmail account. However they didn't favor such an approach because they think gmail is not safe enough.
Any ideas on this?
Thanks!
Comment #3
danepowell commentedI am trying very hard not to be flippant about this, because I understand that it's not your fault, so I'll just say this: Microsoft Exchange is grossly incompatible with a wide number of industry-standard protocols, to which we can now apparently add "POP" and "IMAP". It has been a thorn in the side of Mailhandler for a long time (see #1127706: Extract messageid from body, as a backup to 'in-reply-to' header and #75229: Compatibility with Outlook-generated HTML, just for starters), and I'm very tired of bending over backward to support it.
With specific regard to this issue- we rely on the PHP IMAP library, which I'm sure doesn't support any protocol other than POP or IMAP. Supporting any other protocol would require ripping out the backend of Mailhandler, and replacing it with some other library or custom code to handle MAPI. That's not something that I'm willing to do. However, if it's a project that you'd like to undertake, please do let me know if there's anything that can be changed on Mailhandler's side to assist, such as making the backend library "pluggable". I'm not going to do the legwork on this though, sorry.
Comment #4
pvanerk commentedDane,
Thanks for your extensive comment. I totally agree with you. It's funny to see how big companies think about this. If it's Microsoft, it should be okay. Even top CIOs think like this.
I am going to think about other alternatives. Thanks for your time!
Comment #5
danepowell commentedThanks for understanding. Let me know if there's any other way I can help.
Comment #6
danepowell commentedJust FYI, here's a somewhat related issue that you may want to follow. Although it's also borderline 'won't fix'... #275926: Message retrieval library plugins (in order to avoid PHP IMAP dependency)
Comment #7
danepowell commentedHey, I don't know if this is still an issue for you, but I'm happy to report that this is now a little closer to being possible, now that this issue is fixed: #275926: Message retrieval library plugins (in order to avoid PHP IMAP dependency)
In order to make it work, you'd have to copy MailhandlerPhpImapRetrieve.class.php and adapt it to use MAPI instead of the PHP IMAP library.
Comment #8
pvanerk commentedHi Dane,
Thanks for the info! I will have a look at it.
Comment #9
danepowell commentedI think work on this should probably wait for #1042112: PHP IMAP alternative... there may be some good lessons to be learned in that process that will be easier to learn on an IMAP rather than MAPI library. Baby steps, you know. :)
Comment #10
danepowell commentedComment #11
danepowell commentedComment #12
danepowell commentedI'm happy to review a patch for this but I'm not going to be the one developing it.