CDO Email Question

irish634

Registered User.
Local time
Today, 17:05
Joined
Sep 22, 2008
Messages
230
For those of you using CDO for email automation, which do you prefer?

I have am app with a large # of users with email. Would you:

  1. Require each user to provide their userid and password for authentication OR
  2. Have a company wide generic email for this purpose.
The latter would be much easier I presume.
 
For those of you using CDO for email automation, which do you prefer?

I have am app with a large # of users with email. Would you:

  1. Require each user to provide their userid and password for authentication OR
  2. Have a company wide generic email for this purpose.
The latter would be much easier I presume.

Not sure what your question has to do with using CDO. :confused:

IMHO, we do not have any information with which to based a recommendation.

Which option to use .... well ..... that all depends on your desired results. I would have to ask: why you as sending the email? Will the email need a reply? Do you want to track who sent the email? etc.
 
Not sure what your question has to do with using CDO. :confused:

IMHO, we do not have any information with which to based a recommendation.

Which option to use .... well ..... that all depends on your desired results. I would have to ask: why you as sending the email? Will the email need a reply? Do you want to track who sent the email? etc.

Well, I know that I will need to have a user id and password to send through the server.

For some items it won't matter who sends it. An example would be an auto email for open items for the users that need to approve them (Document revision approval). In this case the generic would work.

The other will be a user submits a document change request etc. So the single user will need to be replied to along with the document change routing. In this case I would ask for the User id and pw of the person sending it.
 

Users who are viewing this thread

Back
Top Bottom