Preferred Email Implementation in Hot Deploy Component

Hi all,

I had a few questions about implementing emails in the framework.

I'm using some out of box applications (such as Party, Order, etc.) in my
custom application. What I've noticed is that there are some emails which
will be automatically generated (such as when the status of an order is
changed, etc.). It seems that these auto generated emails will first check
the Product Store configuration to see if an email for the given type (e.g.
Change of Password) has been defined, and it will use this.

1) If I wanted to effectively "disable" these automatic emails which are
generated from each webapp, is it enough to simply not define that EmailType
in my Product Store, or do I need to hunt down all SECA's and the like which
send these emails and disable them manually?

2) Additionally, in order for me to facilitate emails in my custom
application, I plan to: define new EmailTypes, and configure them in my
ProductStore (along with defining the screen). I'm wondering if this is the
preferred approach?

3) I haven't been able to determine the link between party Communications,
and emails. I noticed that some of the email services will accept a
'communicationEventId' (though optional), and through various SECA's, will
update the status of the communication once the mail is sent (or not sent).

Additionally, there is a scheduled job: "sendEmailDated" which will dispatch
email communications for which the startDate has passed. I'm essentially
just looking to find out whether it's best to:

i) Create a communication event manually
ii) Then directly call the "sendMailFromScreen" service, which attempts to
send out the email from there

OR

i) Create a communication event for the party which will then be picked up
and sent out by the scheduled job

If the latter, does there exist a way to create a communicationEvent for a
party off of a screen definition?

For reference, I'm on the 12.04.02 release

Thanks!