Our internal MS Exchange Server 2003 is setup to receive email on different domains, for example [url removed, login to view], [url removed, login to view] and depararement2.com. However, due to the nature of Exchange, we can only send mail from the primary address, and not any of the users secondary addresses.
I am aware of workarounds such as setting up additional mailboxes for each user, I want to avoid this and have a solution that makes sending email from secondary email addressess straightforward.
The best solution I've found so far is "ChooseFrom":
<[url removed, login to view]>
However, after reviewing this and it's helper applications? (SmartFrom/SmartReply)? I have concerns that the client side of the application is not user friendly enough. I'm therefore looking for a custom solution that is similar but simpler for the end user.
I would like a solution that makes use of the "From" option in the Outlook 2003 new message dialog box, so that instead of the "From" button being used to display the users? address book with email then being sent on "behalf of" the selected address book contact, the "From" button is actually used to display a list of the users various primary and secondary exchange email addresses. I would like to see this done using some sort of api call/event hook, and not by manipulating the users address book contact list, so the address book selection dialog box would never been shown.
If possible, I would like to go one step further, and have the "From" button and associated text box replaced with an Outlook Express style "From" text label and drop down list box showing all the users exchange email addresses. But I realise this may be much more difficult, if not impossible.
I would also like the default "From" address of repliy messages to match the address that the original message was sent to. (Just like the SmartReply solution mentioned above).
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows? (depending on the nature? of the deliverables):
a)? For? server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be either installed by the Seller in ready-to-run condition in the Buyer's environment or the seller must provide detailed installation instructions so the buyer can install the deliverables personally.
b) For client-side deliverables: A standard msi based software? installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
The server side of the solution should run on all versions of Windows Server 2003 (Standard/Enterprise/32bit/64bit/SP0/SP1/SP2/R2 etc) and all versions of Exchange Server 2003 (Standard/Enterprise/SP0/SP1/SP2 etc)
The client side of the solution should run on all versions of? Windows XP (Home/Pro/32bit/64bit/SP0/SP1/SP2 etc) and all versions of Outlook 2003 (SP0/SP1/SP2 etc).