BTW you can write custom email handlers for SharePoint...is that being considered?
JohnH(HP) From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Trevor Andrew Sent: Wednesday, April 02, 2008 9:50 AM To: [email protected] Subject: RE: [OzMOSS] Mail Enabling a SharePoint List Hi Ishai, Thanks for that. I guess also because of your suspicion (which I'll try and verify), that the event handlers don't fire on inbound e-mail, the third option is likely to not be a very good useful either ... With regard to processing outside of SharePoint, I was going to write a relatively simple Windows Service that monitors a mailbox, rather than a solution embedded within Exchange Server infrastructure itself ... I've more expertise with writing Windows Services than with working within Exchange events etc ... Cheers, Trevor From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ishai Sagi Sent: Wednesday, 2 April 2008 9:37 AM To: [email protected] Subject: RE: [OzMOSS] Mail Enabling a SharePoint List I'd be weary of the first one, as I had heard (not experimented though - so you'd better test it yourself and not take my word) that event handlers do not get triggered by the incoming email. As for the second option, if you have exchange server and experience in developing for it you can do that on the server, or otherwise you will have to code against the smtp service. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Trevor Andrew Sent: Wednesday, 2 April 2008 9:13 AM To: [email protected] Cc: Ishai Sagi Subject: [OzMOSS] Mail Enabling a SharePoint List Hi All, We are designing a SharePoint application and we intended to use an e-mail enabled list as the recipient of initial requests. While doing some initial prototypes I've found that it appears the only SharePoint list types that can be e-mail enabled are: * Document Library * Announcements List * Calendar List * Discussion Board In our initial prototyping we used a Document Library, and experimented with the various settings (i.e. save original e-mail, create folder for documents, store in root folder etc). None of the setting combinations seem to deliver just what we want. The e-mails we receive consist of a plain text body with an image attachment, both of which we would like saved, and the attributes of the item need to be populated from values parsed out of the e-mail. The outcome we would like to achieve is that inbound e-mail ends up as: * A list item with attributes filled in with values parsed from the text body of the e-mail. * The item should have two attachments, the original plain text body of the e-mail and the picture attachment from the e-mail I guess my question is how would you recommend we approach this. Alternatives I can see are potentially viable: * Write an event receiver to perform the appropriate parsing / conversion * Parse the e-mails outside of SharePoint, and programmatically create the items in a custom list with the appropriate attachments * Develop a custom list - sounds complex and I'm not even sure how much more simply it would allow us to do what we want I'd really welcome some advice on the best recommended approach to this ... Cheers, Trevor Andre ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com
