18

3

Our IT security won't allow IMAP or POP3 or even S-POP access to an Exchange email account. I already have a fogbugz account set up. Would it be possible to add support for allowing FogBugz to talk to an Exchange server?

Fog Creek Case FC1869871

flag
1 
I concur on a protocol other than POP3 or IMAP, due to company security policy. MAPI, or even an HTTP-based approach (allowing, for example, Outlook "Web Access" email via web page) would definitely be helpful. – Lee Gilchriest Jun 28 at 20:59
HTTP/S-based approach for Exchange 2007 and up, that would be a useful feature. – unknown (google) Nov 16 at 15:56

4 Answers

3

Why not move mail handling into a plugin? I mean just input and output of RFC822 text data should not be so much to implement, since it would basically just be a separation of existing functionality into two plugins.

For inbound mail, the Plugin interface would need to be able to load and save generic values in the CMailbox object and provide a configuration page. It would be polled (heartbeat) and push new messages into FogBugz.

For outbound mail, there could probably only be one plugin, and it would receive messages as strings plus the required metadata (sender and list of recepients).

POP3 and SMTP would be shipped by FogCreek, others could implement plugins for instance for Exchange access via WebDAV or whatever.

link|flag
3

Right now, POP3 gives us all the functionality we need in FogBugz. The only compelling reason for us to add more kinds of support (IMAP, Exchange) is to allow us to get into environments where they don't allow POP3.

We've recognized that this is a dealbreaker in some cases, and that those broken deals cost us money. We will be addressing a number of email issues in future releases and, since this one will actually make us both money and friends, it's likely to happen then.

If you would like to see this functionality in FogBugz, please up-vote the question above.

link|flag
1

Just some more input on this, this is quickly becoming a dealbreaker for us. We're current customers with an internal installation and all protocols were disabled for us last night, except for Exchange. We've been fortunate up until now that IMAP has been available to us and we have implemented a hack to make that work with FogBugz, but that's now gone. We're working on an alternative using MAPI, but the hacking is getting old.

link|flag
Squillman, I'd be interested to hear if you've been able to get something working with MAPI/Exchange. Please give me a call at 646-826-3864. Thanks, Damian – Damian Brown Feb 19 2010 at 16:07
@Damian: MAPI was definitely a no-go after the patch that MS rolled out a while back to require user interaction when programmatically interfacing with MAPI. We actually got it working by hitting Exchange Web Services and pulling the messages in over HTTP(S). I believe this requires at least Exchange 2007 on the backend. One of the other guys on my team wrote the code. I think he was going to work with FogCreek guys to showcase it in their newsletter, but maybe I can at least get a blog post out. – squillman Feb 19 2010 at 20:50
0

Would it be an option to forward or redirect mail to (for example) a Gmail account and link that to FogBugz through POP3?

link|flag

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.