As Rodopi currently only provides authentication for Email Accounts there should be no need to update the stored procedures.

 

If your user base is not very large, I would recommend you look at implementing the Extended Database as this can provide enhanced functionality with little coding effort. What you would do is create the Extended Database and point Modus Mail to authenticate against that. Then create the necessary plans in Rodopi each plan can override the server defaults and can include options such as SPAM scanning and AV scanning (benefit here is you can create a plan with an additional charge for the scanning services). Next you need to create Event Scripts for all the related events. The event scripts can be off SQL Type and can call either a stored procedure or have the statements built-in. They should at least populate the table used by ModusMail with the email address and other required details (you can also add fields pulled from the customer record).

 

If you have a considerable user base I would still recommend the above, however you would need to update all the user accounts within Rodopi. This can be done by upgrading their Plans to a new Email Plan which is set-up with the relevant event scripts. If you try using the exiting email plan you may need to re-fire the event scripts and details for this are available at http://www.rodopi-faq.com (there is a SQL Query to re-fire the event scripts which should work with Rodopi version 5+).

 

 

Regards,
 
Suneel Jhangiani
Inter-Computer Technology Ltd.
 

Modus3 Bug Hunt Winner


Experience is a wonderful thing. It enables you to recognize a mistake when you make it again.

 

 

From: Walter Dearwester [mailto:[EMAIL PROTECTED]
Sent: 14 November 2003 13:25
To: [EMAIL PROTECTED]
Subject: [Modus] Any Change in Stored Procedure with Rodopi?

 

Is there any need to update or change the Rodopi Stored Procedure in moving from Modusmail 1.4 to Modusmail 3.0?

 

TIA

 

Wally Dearwester

CommKey Internet

<<image001.gif>>

Reply via email to