On the one hand, sending Email in aware is easy/straightforward - Ask Vlad.
On the other hand, its complex with lots of twists and turns that you're no where ready to deal with as a newbie.
*) If a user is sending an email to a client, and it bounces, how will he ever know? It wasn't sent from his email account, but from a generic one setup in System Settings. Or if the customer replies, he will never see it.
*) And if it is sent from the generic account, then the client doesn't see it coming from "Max", only from the general account.
*) So then you have to investigate "replies-to"
*) But that has to be diff. for each user, so you have to have that in their User settings, to add to the email.
*) But users want it in their own "Sent Mail" folder, and it won't be if sent from the Generic acct. So a few years back he added "Outgoing Email Account". So you need to set these up and each user has to have their SMTP settings to its coming from their account (some email providers allow 'on behalf of' settings - this is another topic - but generally to prevent spoofing, you can't send from 1 account and say you're someone else).
*) k, if you get this far, you're going to want a "communications" history inside of aware (see CRM demo app) - so thats a physical file (lets call it OutgoingEmail) you CREATE with the TO address, subject, etc. You have to CREATE DOCUMENT the invoice and put it somewhere on the file system, because you need to IMPORT DOCUMENT into the Outgoing Email record you created.
*) THEN you can SEND OutgoingEmail to Contact USING OutgoingEmailAccount
UNLESS you are on UpCloud and you have to build a squirrelly Queue system because of a Java problem between Aware and Upcloud. (this is another few hours of work)
*) If you're doing emails now, and you want to allow a user to reset a password (or forgot password), thats a whole diff. topic because you need to build an encrypted link in the email to allow the user to see "Click here to be logged in", but one of the query parameters is the password, and you can't encrypt the users password if he enters it in the password field because it already encrypted, so when he enters his new password it has to be in a "dummy" field so you can grab it and build the login link (of course a few years ago we found out you can assign the Aware password field to that dummy field and internally it stores the encrypted version - cool, but nobody knew this) yada yada yada, blah blah blah... yes, it gets crazy. Like i said, another topic.
OK, good luck with emails... its Easy!!!
