Show Bid Request Exchange 5.5/SQL - Small Project Bid Request Id: 16836 Bookmark in my 'To Do' list Posted by: vandamme (6 ratings) (Software buyer rating 10) Non-action Ratio: Above Average - 25.00% Buyer Security Verifications: Excellent Approved on: May 20, 2002 9:31:27 AM EDT Bidding Closes: May 24, 2002 9:35:32 AM EDT Viewed (by coders): 262 times Deadline: 5/28/2002 TIME EXPIRED Phase: 100% of work completed and accepted. Coder has been paid. Max Accepted Bid: Bidding is closed Project Type: Small Business Project: $100 (USD) + Bidding Type: Open Auction Categories: Database, MS Exchange Enter chat room for this bid request (0 active users at Aug 28, 2003 9:50:00 PM EDT) Description: Need Exchange (version 5.5) Rule/programming created to do the following: a) Intercept all inbound emails with the words unsubscribe in the subject line. The recipient of the message should not recieve the message but it should be placed in a shared folder called 'eC_Unsubscribe' for future reference. b) Update a SQL table. The database and name of the SQL table should be configurable (either through command file or visual interface) The SQL table will have the following fields: EMAIL varchar(100) - populate with Email of the person who sent (I.e. replied and unsubscribed) the message RCVD_DATE datetime Time the message was recieved MESSAGE_BODY memo Text of message EC_PROCESSED_DATE datetime For our internal use Every message with unsubscribe in the subject should be appended to this table with the apporpriate values. c) Detailed instructions (with screen shots) of how to install the rules and code. d) All of the rules must be at the Server (Echange) level - not Client (Outlook 2000) level. e) Need accurate estimate of when job could be completed by. Deliverables: Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. Complete copyrights to all work purchased. Platform: Exchange 5.5 Microsoft SQL Server 7.0 Must be 100% finished and received by buyer on: May 28, 2002 EDT Deadline legal notes: All times are expressed in the time zone of the site EDT (UT - 5). If the buyer omitted a time, then the deadline is 11:59:59 PM EDT on the indicated date. Remember that contacting the other party outside of the site (by email, phone, etc.) on all business projects < $500 (before the buyer's money is escrowed) is a violation of both the software buyer and seller agreements. We monitor all site activity for such violations and can instantly expel transgressers on the spot, so we thank you in advance for your cooperation. If you notice a violation please help out the site and report it. Thanks for your help.   Bidding/Comments: All monetary amounts on the site are in United States dollars. Rent a Coder is a closed auction, so coders can only see their own bids and comments. Buyers can view every posting made on their bid requests. See all rejected bids (and all comments) Name   Bid Amount    Date   Coder Rating   This bid was accepted by the buyer! alex4 (14 ratings) in Saratov, NA Russian Federation Bid id: 184,016   $120 (USD) May 21, 2002 10:37:56 AM EDT  8.78 (Superb)     Hi, we have similar script and I can modify it according with your requirements. This work will take 2 days. I should note that actually the messages will arrive to mailbox and then will be moved to the shared folder within 1 minute because scripting agent runs once per minute by default. We have Exchange 5.5, MS SQL 7.0 on Windows 2000 server. I will provide instructions to setup the script. Alexander           See 2 private reply(ies) to/from alex4.   alex4 (14 ratings) in Saratov, NA Russian Federation Bid id: 185,879   N/A May 23, 2002 3:51:36 AM EDT  8.78 (Superb)     Hi, I've copied the part of the article from MSDN. It will be helpful for you. Link for the artcile: http://msdn.microsoft.com/library/default.asp?url=/nhp/Default.asp?contentid=28000408 The Microsoft Exchange Event Service fires events asynchronously with respect to the Microsoft Exchange information store. This means that the store does not block your event script, or wait for it to run, before letting other processes access the folder or message. Other processes (Inbox Assistant rules, or even a fast user) could move, copy, delete, or modify the message before your script has a chance to complete or even run. The Microsoft Exchange Scripting Agent is therefore suitable for typical, medium-volume workflow or administrative applications. It is not suitable for applications that would, for example, scan every piece of mail in or out of the system for viruses, or archive every message for government record-keeping purposes, because there is no guarantee that your scripts will see every message. A good example is trying to use OnMessageCreated events in your Outbox folder to process all outgoing mail. By the time your script runs, the message will already have been delivered and deleted from your Outbox.           See 2 private reply(ies) to/from alex4.