Hi all, I am preparing to build a custom application suite and network
solution using Imail for a vertical market. I have some questions though.
My app is a C++ client that will present a 'canned' implementation of a
pop/smtp app (using IPWorks C++ toolkit which I can highly recommend). Some
of the other specs include using SQL 7 to store info for each member of the
network. One of the fields in each record will of course be the user's
email address for this private network. However, over time these
subscribers will be promoted/demoted into different 'groups' based on
criteria that I will maintain and collect from the user.
To be more clear(I hope), with this network I need to dynamically manipulate
a user's group membership within an Imail 'group' or 'list' or whatever the
correct term here may be. That is, as I receive data from my custom client
over time, I'll continually update the user's record in SQL as to which
'type' of user this person is. As this user's 'network' type changes, I
need to modify his/her Imail group membership.
--- USAGE CASE ---
* Network type - something I define and maintain to suit market requirements
* Imail group - the mechanism by which Imail uses to forward mail to N
members via a single Imail username... (not sure if terminology is correct
here)
1.
USER1 starts life as network type1 within Imail group1
[ mail sent to [EMAIL PROTECTED] is sent to USER1 ]
2.
USER1 gets promoted to type2(sql update) and Imail group changes to group2
[ mail sent to [EMAIL PROTECTED] is sent to USER1 ]
N...
USER1 constantly (every few weeks or so) changes network type and a change
to their Imail group membership must be kept in-synch
[ synch'ing network type and Imail group membership as user's record is
updated ]
--- USAGE CASE ---
Does this seem doable? I have no problem with coding the necessary
synchronization routines to make this work, I fully expected to have to do
this. But, does anyone have any suggestions or pointers on how this may
work or not work if that may be the case...
Also, I understand there are some issues, watching the list over the past
few weeks, with keeping Imail working properly when SQL goes down. Does it
seem reasonable that this problem could be solved if I wrote a pair of NT
services that continually monitor the health of each system. Then when SQL
goes down, I could [fill in the blank] do the right thing with Imail (stop
its services until SQL comes back up?). This of course, is how products
like DoubleTake handle failover redundancy. Or, is there another solution
that has already been coded? Any input here would be appreciated. This of
course implies that I plan on keeping the Imail user dbase in SQL 7...
Thanks a bunch,
Chris Douglass
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
