Project Plans by priority please add estimated completion dates

1.)Allow multiple sets of data to be associated with a single email address depending on which list is being mailed to (Jack and Jill use the same email address to sign up on two different sites) 2.)Email upload tool. This would allow and zip/tar file to be uploaded to the server containing one or more files (text, html, link images, embedded images). 3.)Allow grouping of ip-addresses and domains for a company for a campaign. When the email software can keep companies separated then it will be possible to use all mail servers without mixing company ip-address. (If mailing for Yahoo you would not want to use Microsoft's ip-address.) 4.)The steps for setting up a Email Campaign: 1.Select the emailing company. 2.Select which Mailing Ips will be used based on prior ip grouping. 3.Select which redirect Urls will be used and assign a subdomain for this campaign. These domains will also be based upon prior grouping. 4.Select frame forward domain that redirect sites will point to, insert the url to the site that will be frame forwarded to. (www.mygoogle.com frame forwards to http://www.myyahoo.com/affid=111111&campaign=mystuff) 5.Select or Upload the Email Creative. 6.Assign subject line or multiple subject lines. 7.Assign from “Friendly Name” and email prefix like (support@<some domain>, there maybe multiple of these also 8.Preview and/or Test email. Allow sending to a test list before scheduling the full campaign. 9.Select lists / filtered lists / or create a custom campaign list which could be a grouping of lists along with filters. 10.Schedule a time to start send / Schedule a Start and Estimated Completion time / Send now function. 11. Must have a page to check the progress of all scheduled and mailing campaigns. Current status, how much complete, number of bounces, number sent, number received, number of unsubscribes, opens and reads. 5.)Allow the Creation of Filtered Lists, These are just one offs of existing lists, I imagine this as a tree drop down tree structure where you have a Company list but then you choose filters like (State='Nevada' and Sex='Female) creating a sub-list called 'Company A Women in Nevada'. 6.)Allow creation of ISP profiles. This would allow automated customization of an email campaign per ISP. This could contain email rates, number of allowable bounces per ip, usable ip-addresses, and usable domain names. (Often times an ISP will ban a domain name/ip-address, but just because a domain name/ip-address has gone bad at one ISP doesn't mean it can be used for other ISPs). 7.)Modifying user interface to normalize menuing system functions/buttons. This approach allows new menuing buttons/drop downs to appear at the top of the page depending on which tab page we are on. This should cut down on the number of buttons that need to be placed on a page and keep all functionality to a common location. 8.)The ability to associate multiple categories of interest with a user on a list, Jill@… interests are (cars, horses, computers and online dating).

<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server.userException</faultcode><faultstring>org.postgresql.util.PSQLException: The column index is out of range: 0, number of columns: 1.</faultstring><detail><ns1:stackTrace xmlns:ns1="http://xml.apache.org/axis/">org.postgresql.util.PSQLException: The column index is out of range: 0, number of columns: 1.

at org.postgresql.core.v3.SimpleParameterList?.bind(SimpleParameterList?.java:52) at org.postgresql.core.v3.SimpleParameterList?.setLiteralParameter(SimpleParameterList?.java:97) at org.postgresql.jdbc2.AbstractJdbc?2Statement.bindLiteral(AbstractJdbc?2Statement.java:2066) at org.postgresql.jdbc2.AbstractJdbc?2Statement.setInt(AbstractJdbc?2Statement.java:1114) at org.blisted.spamzilla.Campaign.<init>(Campaign.java:82) at org.blisted.spamzilla.Service.startCampaign(Service.java:143) at sun.reflect.NativeMethodAccessorImpl?.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl?.invoke(NativeMethodAccessorImpl?.java:39) at sun.reflect.DelegatingMethodAccessorImpl?.invoke(DelegatingMethodAccessorImpl?.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.axis.providers.java.MsgProvider?.processMessage(MsgProvider?.java:155) at org.apache.axis.providers.java.JavaProvider?.invoke(JavaProvider?.java:323) at org.apache.axis.strategies.InvocationStrategy?.visit(InvocationStrategy?.java:32) at org.apache.axis.SimpleChain?.doVisiting(SimpleChain?.java:118) at org.apache.axis.SimpleChain?.invoke(SimpleChain?.java:83) at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:453) at org.apache.axis.server.AxisServer?.invoke(AxisServer?.java:281) at org.apache.axis.transport.http.SimpleAxisWorker?.execute(SimpleAxisWorker?.java:428) at org.apache.axis.transport.http.SimpleAxisWorker?.run(SimpleAxisWorker?.java:155) at org.apache.axis.transport.http.SimpleAxisServer?.run(SimpleAxisServer?.java:245) at org.apache.axis.transport.http.SimpleAxisServer?.start(SimpleAxisServer?.java:296) at org.apache.axis.transport.http.SimpleAxisServer?.start(SimpleAxisServer?.java:304) at org.apache.axis.transport.http.SimpleAxisServer?.main(SimpleAxisServer?.java:385)

</ns1:stackTrace><ns2:hostname xmlns:ns2="http://xml.apache.org/axis/">2.com</ns2:hostname></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>

I was looking into some ways to manage the hundreds of IPs came across on possible solution. There is a program called BIND DLZ which provides Dynamically Loadable Zones using a database, it will work with Postgresql and could provied and handy solution. If you prefer another way please let me know there are several various ways of doing this but this way does not require you to restart your DNS server when you make a changes and causes DNS to Read directly from a Database.

Please let me know if I missed some steps:

Software Documentation
1.)Campaign Mailing Begins
2.)Database Server creates rDNS and DNS entries for nodes
3.)Database Server passes mailing Ips and Web Ips to nodes
4.)Database Server passes campaign information to nodes
5.)Node requests email template from Database
6.)Node requests subscriber data from Database (ex: 200 list subscribers)
7.)Node merge subscriber data with email template
8.)Node ads any tracking data or header data as needed
9.)Node performs a mx lookup on subscriber email domain
10.)Node looks for any rules to abide by for said mx domain
11.)Node connects to ISP's mx server
12.)Node sends email
13.)Node receives email result status from ISP mx server
14.)Node checks status code against ISP rules
15.)Node takes appropriate action based on status result and ISP rules
16.)Return to Step #7 Until Queue is empty
17.)Return to Step #6 Until Database says complete