Thanks to Tom Molenhouse for sending me an email after reading my article the other day (I love the SharePoint community). The below instructions were found via a cached Google page here:
This script provides incoming email functionality when using WSS 3.0 on a Small Business Server, or on an Exchange Server.
We offer no guarantees that this script will work for you, and we are unable to offer free support.
Instructions
- Download the script here
- Save the script on your server
- Set variables in the script as required
- Create drop directory as you have specified in the script
- Configure WSS at Central Administration > Operations > Incoming E-Mail Settings
- Enable sites on this server to receive e-mail? YES
- Settings mode: ADVANCED
- Use the SharePoint Directory Management Service to create distribution groups and contacts? NO
- E-mail server display address: Enter your email domain name, e.g. yourdomain.com
- E-mail drop folder: As specified in steps 3 and 4
- Click OK! - Create an email enabled list on your WSS site (see below)
- Test the script works by running it manually. Check application event log for errors.
- If all works, then create a scheduled task to run the script as desired. (Start | Control Panel | Scheduled Tasks | Add Scheduled Task).
For step 6. Just go to any SharePoint list e.g. a Shared Documents Document Library and go to Settings. Click on the Incoming e-mail settings link.
You'll see this screen, this is a sample setup.
Naming Standards for Incoming e-mail addresses
On thinking about this they'd have to be some form of naming standards for the incoming list address. So basically you need to create an Active Directory account with an Exchange Mail box for each Incoming E-mail list you require.
How the Script works
The script basically opens the designated Exchange Inbox you map to and for each email there, spins through and writes each one to the drop folder. So you need one of these scripts running for each Inbox you listen to so it's not going to scale that far, but for demonstration purposes is fine.
SharePoint has a watch on this folder as set up in Central Administration in step 5 and it does the magic from here. I'm guessing it must look at the .eml contents and map the to: field to the designated Incoming e-mail settings.
If you use Scheduled Tasks you can only have this running every day, so you'll have to do some smoke and mirrors in the demo or write a cuter app to run this.
These guys have thought of "everything"!
I wonder what happens if you give two SharePoint Lists the same incoming email address?....
...so they thought of this already! Good work! ;-)