cfmail, but it has some smart functionality and a more CFWheels-like approach in general.
config/settings.cfmfile and can look something like this:
cfmaildoes. That's quite a few.
/config/app.cfm: here's an example configuration:
/views/folder, but we recommend a structured, logical approach. If different controllers utilize sendEmail() and each require a unique template, place each email template within the
myemailtemplate.cfm, which will contain HTML content.
myemailtemplatetemplate and passing values for
templateargument should be the path to the view's folder name and template file name without the extension. If the template is in the current controller, then you don't need to specify a folder path to the template file. In that case, just be sure to store the template file in the folder with the rest of the views for that controller.
cfmail? CFWheels is smart enough to figure out that you want to send as HTML since you have tags in the email body. (You can override this behavior if necessary though by passing in the
templatesargument (notice the plural), and CFWheels will automatically figure out which one is text and which one is HTML.
filesargument if you want multiple attachments). Simply pass in the name of a file that exists in the
filesfolder (or a subfolder of it) of your application.
startDate, in the example above) be placed as outputs in the template file.
layoutsarguments (again, notice the plurals), we provide a list of view files to use. CFWheels will figure out which of the templates and layouts are the HTML versions and separate out the MIME parts for you automatically.