Create Program to Mail Email Newsletter

Need Programmer to create from scratch a program to email our newsletter, and configure the server to work with program. See "Deliverables" for details

## Deliverables

Need Programmer to create from scratch a program to email our newsletter, and configure the server to work with program. Program will accomplish the following:

**1.) Reporting**

1.1) Report how many have been sent by day and total, how many errors (listed by type of error), by day and total. 1.

2) Email us when certain errors occur more than X number of times.

**2.) Setup**

2.1) Emailer will function on it's own dedicated Win 2003 server (other OS platforms are possible if you make a good case for not using Win 2003 server)

2.2) Emailer must be extremely reliable, and must be integrated with mail server by programmer. Server configuration will be done by programmer.

2.3) Emailer will use an html file (which we change each mailing) for text/graphics content of each mailing. The html file will be discussed more in 3.4. below.

**3.) Functionality**

3.1)

(a) Emailer will pull email addresses, names, and country, State and postal code, and EmailOffer field from main SQL DB, and put them in a DB table that has additional columns such as MailSent?, DateSent, and TimeZone.

(b) the MailSent and DateSent indicate if the that email has been sent yet, and date sent. (this way, if there is a crash in the middle of the mailing, and we have to restart the mailing, the mailer program knows to only send emails that indicate they have not yet been sent).

(c) The Emailer will need to assign a TimeZone in this column based on looking at the Country, State and Postal Code.

3.2) Emailer by default will send out 100 emails every 10 minutes. But, we will be able to customize both the amount and the time intervals (so it could be send 200 emails every 6 minutes, or whatever we chose).

3.3) Emailer will send out emails based on rules for each time zone of the customer. Let me explain...

(a) We have addresses associated with many of our email addresses, therefore in many cases we know the time zone of the customer (where we do not, we will assume a time zone of EST).

(b) We want to mail customers only during certain times of the day, and on certain days.

(c) Therefore, the Emailer will allow us to set a rule that says, "EST time-zone customers may only be mailed on Monday 10AM-4PM EST, Tuesday 8AM-4PM EST, Wed Not Mailed, Thurs Not Mailed, etc" The goal is to mail each time zone based upon what would be the best time for them to receive the mail. [Later on, we may change this to mail by Country and Time Zone, or by Conteninet and Time-Zone, to try to specifically accomidate that culture (for example in one region Sunday night may be the best time to get email, but not in this other region), but for now we will do it just by time-zone]

(d) To accomplish this, Emailer will need to read Countries and States and Postal Codes to determine the time zone as mentioned above in 3.1.c

3.4) The Emailer will chose between different html files based on the value in the EmailOffer field imported in DB. If the vlue is 1, then the emailer would send [url removed, login to view], if the value is 2, then the emailer would send [url removed, login to view], etc. If there is no value, then it would send the default 1.html.

**4.) Customization** Emailer will use a web page (or Access DB Front end) to allow us to customize settings such as:

4.1) Allow us to specify for each Time-Zone, what time the emailing starts and stops for each day of the week. (e.g. PST time zone we may say Mail only Monday 9AM to 3PM PST, Tuesday 11AM to 5PM PST, Wed Dont mail, etc... and EST we mail specify something totally different). The default will be: Mon 10AM - 3PM, Tu 9:30AM - 4PM, Wed 9:30AM - 4PM, Th 9:30AM - 4PM, Fri 9:30AM - 2PM, Sat Don't Mail, Sun Don't Mail. NOTE: When we talk about a start time of 10AM for a time zone, we are refering to 10AM for that time zone (not 10AM for the server)... So, for clarity, if the customized rule says start email the PST time zone Mondays at 11AM, that is 11AM PST, not 11AM where the server is located/not 11AM server time. The interface for our staff to customize start and stop rules for a time zone will allow them to just put in 10AM, and have it mean 10AM for that time zone, then the Emailer will translate that for the server. Also, Daylight Savings Time will need to be accounted for... so consider that with an option of letting us say "yes account for daylight savings in this time zone", or "no do not"

4.2) As discussed in 3.2 above, how many are emails are mailed out in a group, and how much time between each group. (e.g. We may specify: sending out 100 emails every 10 minutes, or 200 every 6 minutes, etc).

================================== Quality is the top consideration. Start Date: ASAP Beta Due Date: Three Weeks from Start. Release Due Date: Four Weeks From Start

---------------------------------\

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 web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.

b) For all others including desktop software or software the buyer intends to distribute: A 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).

## Platform

Open.

PHP

ID do Projeto: #3558901

Sobre o projeto